3 ms·
https://news.ycombinator.com/item?id=37086022 https://news.ycombinator.com/item?id=37086022
by Piraty 2y ago
https://news.ycombinator.com/item?id=37086022 https://news.ycombinator.com/item?id=37086022
- tome 2y agoWow, my jaw is on the floor. This is such a good idea! I already had the idea of tracking issues in the same repo as the code -- not that I actually use that idea -- but I didn't have the idea of doing PRs in the repo itself. Love it!
- Piraty 2y agotracking issues in the repo would work well. for example, have a dir like ./issues/fix-this-weird-bug.md , and once fixed rename it to ./changelog/fix-this-weird-bug.md . if you adhere to some rules for the metadata, you can use this to base your per-release changelog off of it (some tools already do similar)