/rollout

Commits and pushes all current changes to git, with GitLab issue integration.

Usage

/rollout [#123 | 123 | #new] [--skip-ci]

Parameters

Parameter	Required	Description
Issue ref	No	Issue IID to reference (e.g. #123 or 123)
#new	No	Auto-create a new GitLab issue for this commit
--skip-ci	No	Skip CI/CD pipeline execution

Parameters can be provided in any order.

What It Does

1. Stage and Commit

• Stages all modified files with git add .
• Generates a concise, descriptive commit message
• If an issue reference is provided, appends - fixes #123 to the commit title (GitLab auto-closes the issue on merge)

2. Push

Pushes to the current branch.

3. GitLab Integration

When an issue reference is provided and glab is authenticated:

• Fetches the issue to validate relevance
• Posts a detailed comment summarizing the changes (specific files, what was done, why)
• Updates issue labels to Stage::Completed

Issue Reference Behavior

Scenario	What Happens
/rollout #123	Commits referencing issue #123
/rollout #new	Creates a new GitLab issue automatically, then commits referencing it
/rollout (no ref)	Asks if this was intentional — if confirmed, auto-creates an issue

Every push must reference an issue. If no reference is given and none is created, the command will prompt you.

Auto-Created Issues

When an issue is auto-created, it is:

• Titled as a requirement (not an implementation description)
• Labeled Type::Hotfix
• Written as if it was created before the work was done

Examples

/rollout #2                  # Commit referencing issue #2
/rollout 2                   # Same (# prefix is optional)
/rollout #2 --skip-ci        # Reference issue #2 and skip CI
/rollout #new                # Create issue first, then commit
/rollout #new --skip-ci      # Create issue, commit, skip CI
/rollout                     # Prompts for issue reference

Notes

• AI tools, Claude, or Anthropic are never mentioned in commit messages or GitLab comments
• No Co-Authored-By trailers are added to commits