glab-stack-sync1

Usage

Overview

Updates GitLab to match your local stack:

•

Creates a merge request for each diff without one, unless --skip-mr-creation or --skip-push is set. Each merge request targets the branch of the previous diff, or the base branch for the first diff.

•

Pulls changes made on GitLab, such as applied suggestions, into any diff whose branch is behind its remote.

•

If you amended a diff since the last sync, rebases the diffs after it. Then, unless --skip-push is set, force-pushes the stack's branches.

•

Removes diffs with merged merge requests and deletes their local branches. Keeps diffs with closed merge requests.

•

If you're working in a fork, asks whether to push to the fork or the upstream repository.

•

With --update-base, rebases the stack onto the latest version of the base branch. Then, unless --skip-push is set, force-pushes the stack's branches.

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/.

Options

-a, --assignee=[]
Assign merge request to people by their usernames. Multiple usernames can be comma-separated or specified by repeating the flag.

-l, --label=[]
Add label by name. Multiple labels can be comma-separated or specified by repeating the flag.

--no-verify[=false]
Bypass the pre-push hook. (See githooks(5) for more information.)

--reviewer=[]
Request review from users by their usernames. Multiple usernames can be comma-separated or specified by repeating the flag.

--skip-mr-creation[=false]
Skip creating merge requests for branches that don't have one yet.

--skip-push[=false]
Rebase the stack locally without pushing branches or creating merge requests. Still fetches from the remote and calls the GitLab API.

--update-base[=false]
Rebase the stack onto the latest version of the base branch.

Options inherited from parent commands

-h, --help[=false]
Show help for this command.

-R, --repo=""
Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.

Examples

glab stack sync
glab stack sync --no-verify
glab stack sync --update-base
glab stack sync --skip-push
glab stack sync --skip-mr-creation
glab stack sync --assignee user1,user2
glab stack sync --label bug,priority::high
glab stack sync --reviewer user1 --reviewer user2