Proposal: adding github actions to help automate releases
Hi folks, Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week. One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier: https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like: https://github.com/choldgraf/github-activity to build out a changelog semi-automatically. The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed. I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet. https://github.com/yt-project/yt/pull/2531 -Matt
I love it. +2 Britton On Sat, Apr 11, 2020 at 8:45 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week.
One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier:
https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files
The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like:
https://github.com/choldgraf/github-activity
to build out a changelog semi-automatically.
The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed.
I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet.
https://github.com/yt-project/yt/pull/2531
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
I switched the PR over to use the "mergable" bot: https://github.com/mergeability/mergeable https://github.com/yt-project/yt/pull/2531 Once I get a few more +1's I'll enable the bot and we can see how it works. We can also then disable the existing WIP bot we have. On Mon, Apr 13, 2020 at 7:23 AM Britton Smith <brittonsmith@gmail.com> wrote:
I love it. +2
Britton
On Sat, Apr 11, 2020 at 8:45 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week.
One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier:
https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files
The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like:
https://github.com/choldgraf/github-activity
to build out a changelog semi-automatically.
The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed.
I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet.
https://github.com/yt-project/yt/pull/2531
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
Looks very useful :-) +1
On 13 Apr 2020, at 16:37, Matthew Turk <matthewturk@gmail.com> wrote:
I switched the PR over to use the "mergable" bot:
https://github.com/mergeability/mergeable
https://github.com/yt-project/yt/pull/2531
Once I get a few more +1's I'll enable the bot and we can see how it works. We can also then disable the existing WIP bot we have.
On Mon, Apr 13, 2020 at 7:23 AM Britton Smith <brittonsmith@gmail.com> wrote:
I love it. +2
Britton
On Sat, Apr 11, 2020 at 8:45 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week.
One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier:
https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files
The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like:
https://github.com/choldgraf/github-activity
to build out a changelog semi-automatically.
The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed.
I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet.
https://github.com/yt-project/yt/pull/2531
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
OK, I went ahead and installed the bot, and once this gets merged it should be active: https://github.com/yt-project/yt/pull/2531 On Tue, Apr 14, 2020 at 7:42 AM Clément Robert via yt-dev <yt-dev@python.org> wrote:
Looks very useful :-) +1
On 13 Apr 2020, at 16:37, Matthew Turk <matthewturk@gmail.com> wrote:
I switched the PR over to use the "mergable" bot:
https://github.com/mergeability/mergeable
https://github.com/yt-project/yt/pull/2531
Once I get a few more +1's I'll enable the bot and we can see how it works. We can also then disable the existing WIP bot we have.
On Mon, Apr 13, 2020 at 7:23 AM Britton Smith <brittonsmith@gmail.com> wrote:
I love it. +2
Britton
On Sat, Apr 11, 2020 at 8:45 PM Matthew Turk <matthewturk@gmail.com> wrote:
Hi folks,
Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week.
One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier:
https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files
The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like:
https://github.com/choldgraf/github-activity
to build out a changelog semi-automatically.
The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed.
I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet.
https://github.com/yt-project/yt/pull/2531
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
+1 from me, too! I like the sound of the mergable bot but if it doesn't work out we can switch to a different bot option. No matter what, having something that helps us generate release notes nicely will be a big help! On Mon, Apr 13, 2020 at 9:37 AM Matthew Turk <matthewturk@gmail.com> wrote:
I switched the PR over to use the "mergable" bot:
https://github.com/mergeability/mergeable
https://github.com/yt-project/yt/pull/2531
Once I get a few more +1's I'll enable the bot and we can see how it works. We can also then disable the existing WIP bot we have.
On Mon, Apr 13, 2020 at 7:23 AM Britton Smith <brittonsmith@gmail.com> wrote:
I love it. +2
Britton
On Sat, Apr 11, 2020 at 8:45 PM Matthew Turk <matthewturk@gmail.com>
wrote:
Hi folks,
Madicken did an *amazing* job with the release (which, I know, hasn't been big-time announced yet!) this last week.
One of the bigger pain points seems to be the release notes. I'd like to propose that we enable two specific Github Actions to make this easier:
https://github.com/marketplace/actions/enforce-pr-label https://github.com/marketplace/actions/pr-label-by-files
The first one would be for marking things as bug, docs, tests, new feature, etc, before merging. The second one would be to add labels for PRs based on which files they touch. I'd like to propose that we do this so that we can use a tool like:
https://github.com/choldgraf/github-activity
to build out a changelog semi-automatically.
The per-files labels would be just for the frontends -- so that we could have a label for each frontend, and then in the release notes, collect changes based on which frontend they applied to. This way, we'd have sections for bugs, major features, and then also a separation based on specific frontends, to make it easier to see what has changed.
I've issued a PR that sets up the config for the first action -- the second one would need some modification to our current labels. Neither action has been "enabled" yet.
https://github.com/yt-project/yt/pull/2531
-Matt _______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
_______________________________________________ yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
yt-dev mailing list -- yt-dev@python.org To unsubscribe send an email to yt-dev-leave@python.org
participants (4)
-
Britton Smith -
Clément Robert -
Madicken Munk -
Matthew Turk