You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bukama (via GitHub)" <gi...@apache.org> on 2025/11/09 17:13:38 UTC
[I] Job that creates issue if no open milestone is there [maven-gh-actions-shared]
Bukama opened a new issue, #208:
URL: https://github.com/apache/maven-gh-actions-shared/issues/208
### New feature, improvement proposal
Since we create release notes on Github it's crucial that we have a milestone for each branch a PR is merged into. However I noticed multiple times in the past months that especially after a release no new milestone is created, resulting in comments in PR that the PR can't be associated to a milestone.
I suggest to have a pipeline job for each repository which runs at least once a day (and maybe in addition after a release was made) to check if a new milestone was created. If yes - all fine. If not, create an issue (which also results in a mail send to ML).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Job that creates issue if no open milestone is there [maven-gh-actions-shared]
Posted by "Bukama (via GitHub)" <gi...@apache.org>.
Bukama commented on issue #208:
URL: https://github.com/apache/maven-gh-actions-shared/issues/208#issuecomment-3569457393
> I thinking to take a action in release-drafter pipeline on commit with message
>
> `[maven-release-plugin] prepare release xxx` - close current milestone `[maven-release-plugin] prepare for next development iteration` - create new milestone for branch
As stated in the PR: This will only work in repositories where the milestone setup is correct and will reduce the manual work when doing the release - which is great! Thanks for this <3
My thoughts about this issues is more to continous monitor and check for invalid milestone setups to reduce manual work when PR are merged ("can't identify milestone, please assign proper milestone..." things), which is also the base the automatic milestone handling can work properly :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Job that creates issue if no open milestone is there [maven-gh-actions-shared]
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski commented on issue #208:
URL: https://github.com/apache/maven-gh-actions-shared/issues/208#issuecomment-3508546676
I thinking to take a action in release-drafter pipeline
on commit with message
`[maven-release-plugin] prepare release xxx` - close current milestone
`[maven-release-plugin] prepare for next development iteration` - create new milestone for branch
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org