Skip to content

Commit e29e4ee

Browse files
committed
docs: simplify GitLab mirror section
1 parent 2033956 commit e29e4ee

File tree

1 file changed

+1
-16
lines changed

1 file changed

+1
-16
lines changed

docs/RELEASE_BRANCHES.md

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -31,22 +31,7 @@ A GitHub ruleset already protects all branches matching `release/**` with the sa
3131

3232
### 3. GitLab mirror
3333

34-
The GitLab mirror at `gitlab.cee.redhat.com/rhel-lightspeed/enhanced-shell/okp-mcp` pulls from GitHub. It must be configured to include release branches.
35-
36-
To update the mirror regex:
37-
38-
1. Go to GitLab repo **Settings > Repository > Mirroring repositories**
39-
2. Delete the existing mirror rule (it can't be edited in-place)
40-
3. Create a new Pull mirror with:
41-
- **Git repository URL**: `https://github.com/rhel-lightspeed/okp-mcp.git` (must end in `.git`)
42-
- **Mirror direction**: Pull
43-
- **Mirror branches**: Mirror specific branches
44-
- **Branch regex**: `(main|release\/.*)`
45-
- **Overwrite diverged branches**: checked
46-
- **Trigger pipelines for mirror updates**: checked
47-
4. Click **Mirror repository**
48-
5. Click the sync button (🔄) to trigger an immediate pull
49-
6. Verify the release branch appears in the GitLab branch dropdown
34+
The GitLab mirror at `gitlab.cee.redhat.com/rhel-lightspeed/enhanced-shell/okp-mcp` automatically pulls `main` and any branch matching `release/*` from GitHub. New release branches will appear on GitLab after the next mirror sync (typically within minutes).
5035

5136
**Note:** "Mirror only protected branches" does not reliably detect GitHub ruleset-based protection. Use "Mirror specific branches" with a regex instead.
5237

0 commit comments

Comments
 (0)