Closed MangelMaxime closed 2 weeks ago
If a code repository is not set up to use auto-formatting, you should not use a formatter in your PR! I tried to address this in https://github.com/ionide/KeepAChangelog/pull/24, but as long as the current code is not being checked on every commit you should not use a formatter.
This would have saved you a lot of effort, to be honest πΈ
I agree problem was that it was setup to use it on save and saw it too late.
I will re-send the PR without the formatting change.
I am closing because I think going in the direction from #17 makes more sense.
Out sourcing the parser works would make it easier to maintain Ionide.KeepAChangelog.
WHAT
copilot:summary
copilot:poem
copilot:emoji
WHY
HOW
copilot:walkthrough
Sorry for the big PR, the auto formatting didn't help on that here π
I think copilot for PR is not available anymore so I will write a good old description myself ahah.
Releases
from a list of tuple to using a list of record has we are starting to have a lot of propertiesI was not able to test the
Ionide.KeepAChangelog.Tasks
project because when packing it there seems to be missing somedll
.I think this is something that was discovered with the last release already