Repository navigation
feat: gate issue_write and get_issue behind remote_mcp_issue_fields flag #2558
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
Merged
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
eacc281
feat: gate issue_write and get_issue behind remote_mcp_issue_fields flag
SamMorrowDrums 39dfc2f
refactor: inline IssueWrite/LegacyIssueWrite as full duplicates
SamMorrowDrums eb1aed8
test: add Test_GetIssue_FieldValues_FlagOn to cover the enrichment path
SamMorrowDrums 0ee3ef6
fix: make mergeIssueFieldValues output order deterministic
SamMorrowDrums e3d7f90
Merge branch 'main' into sammorrowdrums/gate-issue-write
SamMorrowDrums 839eb03
Merge branch 'main' into sammorrowdrums/gate-issue-write
SamMorrowDrums 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
refactor: inline IssueWrite/LegacyIssueWrite as full duplicates
Replace the shared buildIssueWrite(includeIssueFields) helper with two fully duplicated tool definitions. When the FeatureFlagIssueFields flag is retired, LegacyIssueWrite can be deleted as a single function with no merge thinking required. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Loading branch information
commit 39dfc2fff01a970eaff00f25571df529ab653238
Some comments aren't visible on the classic Files Changed page.
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
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.
Do we need to add this flag to
set_issue_fieldsas well? It currently is still available whenissues_granularis enabled. Does that need to also have theremote_mcp_issue_fieldsflag enabled, so that issue field writes are consistently behind the same flag?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.
Issues granular I'm ok with having it alreayd.