Limit the canary list to repos this fork can write to - #86
Merged
Merged
Conversation
The canary registry still carried stranske/Travel-Plan-Permission and stranske/Portable-Alpha-Extension-Model from upstream. This fork has no write access to either, so every consumer sync run fails on both and the failure issue it opens is noise that hides real sync problems. Leaves iamkayleb/bukay as the sole canary. Restore the upstream entries only if this fork is ever given write access to them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5
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.
The canary registry still carried stranske/Travel-Plan-Permission and stranske/Portable-Alpha-Extension-Model from upstream. This fork has no write access to either, so every consumer sync run fails on both and the failure issue it opens is noise that hides real sync problems.
Leaves iamkayleb/bukay as the sole canary. Restore the upstream entries only if this fork is ever given write access to them.
Claude-Session: https://claude.ai/code/session_01FC8XoyssN5v6hQCTtcjoB5
Workflow Source
Started from:
Automation intent:
Notes:
Summary
Testing