Skip to content

ci(mirror): remove Copilot automation from stale patch workflow - #13

Merged
TonybynMp4 merged 1 commit into
mainfrom
t3code/remove-mirror-copilot-file-issue
Sep 17, 2026
Merged

TonybynMp4 merged 1 commit into
mainfrom
t3code/remove-mirror-copilot-file-issue

Conversation

@TonybynMp4

Copy link
Copy Markdown
Owner

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 logic
  • Copilot token handling and environment variable setup
  • All references to "Copilot" in workflow and script comments

Changed:

  • Issue template now mentions @$GITHUB_REPOSITORY_OWNER instead of requesting Copilot fixes
  • Workflow step renamed from "Hand the stale patch to Copilot" to "File an issue about the stale patch"
  • Updated guidance in issue body to emphasize manual review instead of automated fixing

Why

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

  • This PR is small and focused
  • I explained what changed and why
  • I included before/after screenshots for any UI changes
  • I included a video for animation/interaction changes

- 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
@TonybynMp4
TonybynMp4 merged commit 4ed6661 into main Sep 17, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant