fix(ci): make auto-tag remote portable across renames/transfers#628
Merged
Conversation
The auto-tag workflow set the SSH remote to a hardcoded
`git@github.com:DFXswiss/realunit-app.git`. After the repo moved to a
different org/name, the next tag push would have failed (or relied on
GitHub's 301 redirect, which git-over-SSH does not follow reliably).
`${{ github.repository }}` resolves to the current `<owner>/<repo>`
of the workflow run, so the remote follows the repo automatically across
renames and transfers.
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
auto-tag.yamlset the SSH remote to a hardcodedgit@github.com:DFXswiss/realunit-app.git. After the recent transfer toRealUnitCH/app, the next tag push would either rely on GitHub's 301 redirect (whichgit pushover SSH does not follow reliably) or fail outright.Switching to
${{ github.repository }}resolves to the current<owner>/<repo>of the workflow run, so the remote tracks the repo automatically across future renames and transfers.Verification
${{ }}substitution).auto-tag.yamland the tag lands cleanly on the new origin.