Initial Issue Triage was adding needs-team-triage incorrectly #7852
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
JimSuplizio
added
the
GitHub Event Processor
jsquire
approved these changes
Mar 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 Issue in azure-sdk-for-java was processed using the new InitialIssueTriage rule and incorrectly had needs-team-triage added to it.
needs-team-triage should only be added in the case of no AzureSdkOwners and no ServiceOwners and is correctly done in that case but there looks to be a stray call to
gitHubEventClient.AddLabel(TriageLabelConstants.NeedsTeamTriage);which was after the check to see if needs-team-attention was being added.