-
Notifications
You must be signed in to change notification settings - Fork 268
Fix context is not defined crash in safeoutputs MCP server on create_pull_request
#18939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+78
−5
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
454a491
Initial plan
Copilot a5ab289
Fix: safeoutputs MCP server crashes with context is not defined on cr…
Copilot 952f6cb
Fix resolveAndValidateRepo regression and test env isolation
Copilot b4f2f38
Fix test env isolation: check context before GITHUB_REPOSITORY
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new
!defaultTargetRepoguard returns an error even whenitem.repois explicitly provided. This is a behavior regression for tools/messages that support arepooverride (e.g.,unassign_from_userinsafe_outputs_tools.json), where operations should still be able to proceed (and be validated againstallowedRepos) even if the default repo can’t be inferred. Consider only erroring when both the resolved repo (after trimming) is empty and there’s noitem.repo, or moving repo selection (itemRepo) before the guard and checking that instead.This issue also appears on line 112 of the same file.
See below for a potential fix:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 952f6cb.
resolveAndValidateReponow extractsitem.repofirst and only errors when bothitem.repoanddefaultTargetRepoare empty, following the suggested pattern. I also updatedvalidateRepoto receivetrimmedDefaultTargetRepoand added a test for the item.repo-with-empty-default case.