Push pipeline branches to the org repository - #844
Merged
Conversation
The pipeline skills assumed origin was a personal fork and upstream the org repository. This checkout has one remote, origin, pointing at the org, so crypter-step-plan failed on its first command and the push step had no upstream/stable to sync a fork from. Branches now go to the org repository the way every branch before the pipeline did, which removes the fork sync push and the second pull request that had to be opened by hand afterwards. crypter-step-open-pull-request checks origin before pushing, since a checkout wired up differently sends the branch somewhere the pull request will not find it. Container-side skills keep the upstream remote name. That is the name the container's own clone gives its single read-only remote, and it is unaffected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The pipeline skills assumed
originwas a personal fork andupstreamthe org repository. A checkout with oneoriginremote pointing at the org fails oncrypter-step-plan's first command, and the push step has noupstream/stableto sync a fork from.Branches now go to the org repository directly. That removes the fork sync push and the second pull request that had to be opened by hand afterwards, so a
/crypter-changerun ends at one draft pull request.crypter-step-open-pull-requestchecksoriginbefore it pushes.Container-side skills keep
upstream— that is the name the container's own clone gives its single read-only remote, and it is unaffected by this. The pipeline doc now says so, since the same repository having two names across the boundary is otherwise a trap.The doc also loses its "Enable Actions on your fork" section, which no longer applies.