Automatically push main and close the latest milestone upon release
#7
Comments
|
#66 took care of pushing the |
dscho
added a commit
to dscho/gfw-helper-github-app
that referenced
this issue
Feb 23, 2024
This is a work in progress! The idea is that as part of closing a `[New git release]` ticket that is associated with a Git for Windows release, we will close the current milestone and open the next one. The current work-in-progress script was used to successfully close the v2.44.0 milestone and open the `Next release` one. So what's missing? This: - The current script needs to be replaced by a proper route in `index.js` - More validations are needed, so that we do not close, say, a milestone that does not even have any issues assigned to it. Or a milestone that is for another version. - Tests. This will address git-for-windows#7. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a release creates a tag that points to the PR branch of a still-open "Rebase to "-class PR, we know that the branch should be pushed and the milestone should be closed out and a new "Next release" milestone should be opened.
Totally automatable.
The text was updated successfully, but these errors were encountered: