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-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. ⭐
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. (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. 🫢

πŸ“ 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 🌈


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