ci(mirror): remove Copilot automation from stale patch workflow - #13
Merged
Merged
Conversation
- Remove automatic Copilot agent assignment from mirror patch issues - Simplify to just filing an issue with repository owner mention - Remove MIRROR_COPILOT_TOKEN and related GraphQL assignment logic - Update workflow step and documentation comments
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
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.
What Changed
Removed automatic Copilot assignment from the mirror patch stale detection workflow. The workflow now files an issue mentioning the repository owner instead of attempting to automatically assign and fix stale patches.
Removed:
request_copilot_fix()function and all Copilot GraphQL assignment logicChanged:
@$GITHUB_REPOSITORY_OWNERinstead of requesting Copilot fixesWhy
Mirror patches are critical infrastructure—a patch that applies but no longer does the right thing silently breaks in-app updates. This requires human judgment and review, not automation.
Filing an issue with the repository owner notification is sufficient and clearer than attempting automatic assignment. It ensures the right people see the problem without relying on agent capabilities that may not apply well to this specific task.
Checklist