scientific-python / attach-next-milestone-action Goto Github PK

I am interesting in this but I am surprised it does not need a Dockerfile and entrypoint shell script, since the Action was written in Python and not browser-native language like NodeJS. Is this being used anywhere? I wish to see how it is working in production. Thanks!

To remove the security warning, theoretically you could run this action only on push commit to main, then you can check if it is a merge commit and if the merge commit was created from merging a PR. If not, then just a no-op, but yes, then you run the milestone thingy.

You might be able to take advantage of browser-native functionality that GitHub provides, like https://github.com/octokit/action.js/

The downside is that maintainer needs to touch JS.

Some projects have release branches. In those cases, they might use the backport bot to open a backport PR to the backport branch of something that is already merged into main. Or they can be doing a manual backport.

Would be nice to be able to auto milestone those too.

Example:

1. PR 1234 was merged into main. Got auto-milestoned to next major/minor release (depending how strict of a semver follower you are).
2. Backport bot opens PR 1235 that backports PR 1234 to v0.1.x branch. Would be nice if this gets auto-milestone to the next bugfix release milestone in the v0.1.x series.

E.g. release blocker PRs could be manually milestones while in the PR phase, the action should leave these alone.