Closed chandlerprall closed 2 years ago
This might be implied, but we could change our GitHub PR template to include text/example on how to properly write the entry in the PR description.
This might be implied
Thank you for stating it explicitly :)
We can probably do something with semantic-release and commitizen. I'll see if I can find some time to look into this.
Thanks for thinking on this @pugnascotia, but we had already decided unanimously that we don't want to be restricted in the way we write our commit messages.
Works for me. I’ll close the issue then.
Sorry, I didn't mean to say that we weren't still looking into automated Changelogs, we just don't want to be forced into writing our commits in a restricted way. I believe @chandlerprall has a path he's expoloring.
^ correct, copy/pasting from the above description:
To address this, let's explore including the changelog entry as part of the PR description and have the release script find PR's since the last change set and inspect them for descriptions, updating the changelog.
GitHub Actions are enabled in the repo now, and I'm guessing that exploring workflows would be worthwhile.
https://github.com/marketplace/actions/release-drafter is a thing, too
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.
We're now using actions, and so there is probably something we can do to automate this.
Closing this because of the upcoming_changelogs
flow. Feel free to reopen if anyone disagrees.
Our current method of updating CHANGELOG.md as part of a pull request creates some friction, including
To address this, let's explore including the changelog entry as part of the PR description and have the release script find PR's since the last change set and inspect them for descriptions, updating the changelog.