chore: remove duplicate, broken upstream_sync workflow - #13
Merged
Conversation
upstream-sync.yml (hyphenated) already syncs daily and has succeeded on every recent run using the default GITHUB_TOKEN. upstream_sync.yml (underscored) duplicated the same job every 4 hours instead, but has failed every run with a 403 at checkout: fatal: unable to access 'https://github.com/SharpAI/mlx-swift/': The requested URL returned error: 403 It overrides the checkout token with SWIFTLM_PR_TOKEN, which is configured as a secret on this repo but rejected by GitHub for this operation. Since the working sibling workflow proves the default token is sufficient for this repo's sync needs, the fix is to drop the redundant, broken duplicate rather than repair a credential that can't be inspected or rotated from here.
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.
Summary
upstream-sync.yml(hyphenated, daily, 10/10 recent runs succeeded) andupstream_sync.yml(underscored, every 4h, 10/10 recent runs failed).secrets.SWIFTLM_PR_TOKEN(confirmed present on this repo via the API, but rejected here — likely expired or wrong scope; I can't inspect or rotate a secret's value). The working sibling workflow does the same job using only the defaultGITHUB_TOKEN, which proves that credential is sufficient for this repo's actual sync needs.Test plan
upstream-sync.ymlcontinues to run successfully on its next scheduled trigger.