Repository navigation
ci: keep only CI enabled on the fork - #70
Merged
Merged
Conversation
Other workflows are disabled in GitHub settings instead of edited, so upstream syncs stay conflict-free. Revert the now-unused fingerprint-check runner patch and document the post-sync workflow check.
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
1 participant
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.
Every workflow the fork inherited from upstream except CI either needs Blacksmith runners, Expo, release secrets, or upstream-only integrations. Blacksmith jobs never got a runner here: they sat queued for 24 hours and then got cancelled. The nightly Release queue had filled to 100 pending runs and new scheduled runs were failing immediately. Nothing was billed. Every job that actually ran used free GitHub-hosted runners.
The fix is mostly outside this diff. The other 17 workflows are disabled in the repository settings with
gh workflow disable, and the 101 stuck Release runs are cancelled. Workflow files keep their upstream contents, so syncs don't conflict on them.This PR:
mobile-fingerprint-check.ymlrunner patch now that the workflow is disabled.ci.ymlis the only workflow file that still differs from upstream.docs/personal-fork-changes.md.SYNC.md. New or renamed upstream workflows start enabled, so agents must disable them and cancel their queued runs. New Blacksmith jobs inci.ymlget the same repository-aware runner selection.Done by Claude Opus 5.5 in Claude Code (T3 Code).