Skip to content

Document GitLab service-account identity and per-user connections#1

Open
nkoorty wants to merge 1 commit into
mainfrom
docs/gitlab-service-account-identity
Open

Document GitLab service-account identity and per-user connections#1
nkoorty wants to merge 1 commit into
mainfrom
docs/gitlab-service-account-identity

Conversation

@nkoorty

@nkoorty nkoorty commented Jun 29, 2026

Copy link
Copy Markdown
Member

What

Reframes the GitLab connection docs around identity / attribution, so write-backs (MR comments, fix MRs, commits) are clearly attributed to Gecko rather than whichever person provided the token.

connect/gitlab.mdx (live)

  • Splits the token step into Create a dedicated service accountCreate an access token.
  • Explains why a service account matters: write-backs are authored by the token owner, so a service account keeps activity attributed to "Gecko," survives offboarding, and mirrors the GitHub gecko[bot] identity.
  • Calls out GitLab native Service accounts (Premium/Ultimate) with a gecko-bot fallback on Free.
  • Adds an attribution note under "What Gecko uses the token for."

connect/personal-connections.mdx (new — DRAFT, not in nav)

  • Specifies the target per-user linking model: team service account + opt-in personal connections, with a what-gets-attributed-to-whom table, link/authorize flow (OAuth for .com, PAT for self-managed), fallback rules, and troubleshooting.
  • Deliberately kept out of docs.json navigation and marked {/* DRAFT */} because the feature is not yet implemented. Wire into nav when it ships.

Note

The per-user linking page documents intended behavior, not shipped behavior — it doubles as the spec for the eventual build (per-member token store + token selection in the GitLab write paths + Personal Connections UI).

🤖 Generated with Claude Code

Lead the GitLab connect flow with a dedicated service account so write-backs
(MR comments, fix MRs) are attributed to "Gecko" rather than the individual
who provided the token, mirroring the GitHub gecko[bot] identity.

Add a draft connect/personal-connections.mdx specifying the target per-user
linking model (team service account + opt-in personal connections). Kept out
of docs.json navigation until the feature ships.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 29, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
geckosecurity 🟢 Ready View Preview Jun 29, 2026, 3:48 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant