gitlab mr

Documentation Community

Skill notes

Rules

Never use the skip-doc-check label — every MR must have a real documentation link User Story must be relevant to the MR changes — CI checks relevance (check:mr-us-relevance); irrelevant links will be rejected Blob links must point to pushed files — the branch name and file path in the link must exist on the remote Verify with APIs, don't guess — confirm results at every step using glab commands

Step 1: Check Prerequisites

If there are uncommitted changes, commit or stash them first.

Step 2: Ensure Documentation Exists

The MR description must contain documentation links. CI performs two checks: check:mr-documentation: whether the link format is valid check:mr-us-relevance: whether the linked document is relevant to the MR changes Prefer GitLab blob links pointing to documentation files within the repository. 2a: Find or Create Documentation

Step 4: Create or Update MR

Check if an MR already exists If no MR exists, create one Analyze all commits in git log main..HEAD to write the MR title and description. Blob link format: https://gitlab.example.com/<group>/<project>/-/blob/<branch>/<filepath> <group>/<project> parsed from git remote get-url origin

Step 5: Wait and Check Pipeline

After creating/updating the MR, wait for the pipeline to trigger and complete. If the pipeline is still running, wait and check again:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview gitlab-mr.preview
# Full Workflow Example

# Create MR
glab mr create --title "feat: add retry logic" --description "..." --push

# Loop until CI passes
glab ci status  # -> if failed, check logs, fix -> check again

# After CI passes, check merge status
glab mr view feat/add-retry-logic
# -> conflicts? rebase to resolve -> force push -> wait for new CI

# Final confirmation: CI all green + no conflicts -> report MR URL

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.