You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We risk forgetting to add a milestone to our PRs for the next release, which makes the release manager's job harder. Is there some GitHub workflow that could do that for us?
The text was updated successfully, but these errors were encountered:
It might in theory check the lucene/CHANGES.txt to look for an entry (with the PR/issue number) summarizing the PR? Then it could see which Lucene release the issue is under.
This would also serve to validate that CHANGES.txt was updated (we also often forget this). But ... many PRs are trivial and don't require a CHANGES.txt entry, so I guess we'd need some escape hatch to tell the bot it's OK.
Description
We risk forgetting to add a milestone to our PRs for the next release, which makes the release manager's job harder. Is there some GitHub workflow that could do that for us?
The text was updated successfully, but these errors were encountered: