Set milestone of the issue to newly created relnotes tracking issue #1841
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is useful when the label(s) are added **after** the PR or issue has received the milestone in which case we may never set the milestone in the relnotes tracking issue.
Mark-Simulacrum
approved these changes
Sep 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR set milestone of the issue (if it has one) to newly created relnotes tracking issue.
This is useful if the triggering label(s) is/are added after the PR or issue has received the milestone (because it has already been merged or a milestone has already been assigned to that issue), otherwise we may never set it as we may never receive a new webhook event for that PR/issue.