glab(1)
π NAME π
Okay bestie, welcome to the glab(1) manual page for glab-stack-sync β it pushes the stack to GitLab, and creates or updates its merge requests. (EXPERIMENTAL) π«Ά
β¨ SYNOPSIS β¨
glab stack sync [flags]
πΈ DESCRIPTION πΈ
This command updates GitLab so it matches your local stack, and itβs giving βkeep everything in syncβ main character energy:
- Creates a merge request for each diff without one, unless
--skip-mr-creationor--skip-pushis 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-pushis 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-pushis set, force-pushes the stackβs branches. β
Heads up, bestie: 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. (Seegithooks(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 eitherOWNER/REPOorGROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. π«Ά
π EXAMPLE π
Run these cuties exactly like this:
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
π SEE ALSO π
glab-stack(1)β go give it a lil read, bestie π
mwah π β auto generated by spf13/cobra, dated Nov 2026, and this whole thing is the glab(1) manual page. periodt β¨
π¦ where this page comes from
- arch rolling: glab 1.128.0-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms