Repository navigation
feat(promotion): add selected workflow sync and repository discovery - #36
Merged
Merged
Conversation
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
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.
What / why
Add project-scoped promotion so users can review and sync selected workflow changes through the project's resolved Git connection. Add GitLab repository/branch discovery and commands to continue blocked applies after binding setup.
Changes
promotion provider repositoriesandbranches, with search, escaped repository paths, and bounded cursor collection that follows short or empty non-final pages.promotion project changes,apply, andpromote. Project apply can delete selected workflows absent from the branch; project promote pushes selected workflow states without force support.promotion apply-continueandpromotion project apply-continue. Support explicit expected-source flags or--expected-from FILE|-, required source validation on continue, and strict JSON request input.Verification
make checkpasses locally: formatting, vet, staticcheck, unit tests, race tests, five cross-platform builds, tidy check, and vulnerability scan.make docsrun after help changes and again after the final rebase check.v*tag or release commit in this PR.Notes for reviewer
Behavior is derived from
openapi.upstream.yml1.1.1 and verified with local HTTP fixtures. Live integration tests skipped because instance URL/API key are unset. Integration coverage is read-only; it never applies, promotes, or creates checkouts on a shared instance.Uses the agreed command layout: separate
apply-continuecommands and project operations underpromotion project. Continue is stateless and requires the full workflow selection again for project applies; destructive confirmation covers all applicable changes at continue time, including unreviewed changes.