Restrict /relevance-check slash command to authorized roles#489
Merged
brunoborges merged 1 commit intomainfrom Feb 26, 2026
Merged
Restrict /relevance-check slash command to authorized roles#489brunoborges merged 1 commit intomainfrom
brunoborges merged 1 commit intomainfrom
Conversation
…te roles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brunoborges
force-pushed
the
restrict-relevance-check-roles
branch
from
8622e48 to
fc92356
Compare
|
johnoliver
approved these changes
Feb 26, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds explicit
roles: [admin, maintainer, write]to the/relevance-checkagentic workflow so only users with admin, maintainer, or write permissions can trigger it. This prevents unauthorized users from invoking the command in public issues/PRs.