DO NOT POST ISSUES HERE

[OttoWinter]

For bug reports, please go to https://github.com/esphome/issues/issues

For feature requests, go to https://github.com/esphome/feature-requests/issues

Thank you!

[Fusseldieb]

Why that? It's kinda unintuitive having two separate empty repos just for that...

Better make a badge with "Bug" or "Feature Request" and you can then search by badges.

[h0jeZvgoxFepBQ2C]

Is there any reason why this is like it is? Just asking, no offense :)

[OttoWinter]

@h0jeZvgoxFepBQ2C It's mostly because of this repo's history (IIRC, it's been some time). First, esphomelib was C++-only project (where users had to type C++ themselves), then esphomeyaml was added as a layer that generates the C++ from YAML (that is this repo today).

Back then the issue was that users would create issues randomly split between in the esphomelib and -yaml repos, which made the bug tracker hard to use. So the bug tracker was moved to a separate bug-tracker only repo.

Then the C++ codebase got merged into this project and everything was renamed esphome. Changing the bug/feature tracker now would be quite hard.

[ghost]

1

[Tofandel]

It's technically possible to move issues from one project to another one by one, so maybe a dev console script or puppeteer script
with the correct label could automate this, with a total of 6000 issues it might take a while though but is doable, maybe only moving the open ones is an option
Reaching out to github is also an option, they should be able to do this for you

[davidglezz]

I think it would be easy to make a script that transfers all the issues to this repo using https://cli.github.com/manual/gh_issue_transfer

Examples:

• https://jloh.co/posts/bulk-migrate-issues-github-cli/
• https://medium.com/@devinschumacher/how-to-bulk-transfer-github-issues-from-repository-a-to-repository-b-38255e081096