| title | stage | group | info |
|---|---|---|---|
`glab stack sync` |
Create |
Code Review |
To determine the technical writer assigned to the Stage/Group associated with this page, see <https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments> |
Sync and submit progress on a stacked diff. (EXPERIMENTAL)
Sync and submit progress on a stacked diff. This command runs these steps:
- Optional. If working in a fork, select whether to push to the fork, or the upstream repository.
- Optional. If --update-base is set, rebases the entire stack onto the latest version of the base branch.
- Pushes any amended changes to their merge requests.
- Rebases any changes that happened previously in the stack.
- Removes any branches that were already merged, or with a closed merge request.
This feature is an experiment and is not ready for production use. It might be unstable or removed at any time. For more information, see https://docs.gitlab.com/policy/development_stages_support/.
glab stack sync [flags]
glab stack sync
glab stack sync --no-verify
glab stack sync --update-base --no-verify Bypass the pre-push hook. (See githooks(5) for more information.)
--update-base Rebase the stack onto the latest version of the base branch.
-h, --help Show help for this command.
-R, --repo OWNER/REPO Select another repository. Can use either OWNER/REPO or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.