From 362d294f91d2ad995d516a13768ed3b8c999ab92 Mon Sep 17 00:00:00 2001 From: maekuss Date: Wed, 10 Jun 2026 14:44:18 +0800 Subject: [PATCH 1/3] docs: document self-hosted GitLab / GitLab Enterprise support Add a section to the GitLab integration page covering self-hosted GitLab and GitLab Enterprise via the same Personal Access Token flow, with the one extra step of selecting "Self-hosted / GitLab Enterprise" and entering the instance base URL in the Connect GitLab modal. Note the self-hosted prerequisites (network reachability and token scopes on the instance). Co-Authored-By: Claude Opus 4.8 (1M context) --- platform/repositories/gitlab.mdx | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/platform/repositories/gitlab.mdx b/platform/repositories/gitlab.mdx index 8a969d1..1a0d313 100644 --- a/platform/repositories/gitlab.mdx +++ b/platform/repositories/gitlab.mdx @@ -1,6 +1,6 @@ --- title: "GitLab" -description: "Configure repository access for GitLab.com." +description: "Configure repository access for GitLab.com and self-hosted GitLab." --- ## Prerequisites @@ -72,3 +72,25 @@ This is required to create a service account for Hacktron to use. That's it! Hacktron will now run security reviews for every pull request in the selected repositories. + +## Self-hosted GitLab / GitLab Enterprise + +Hacktron supports self-hosted GitLab and GitLab Enterprise through the same +Personal Access Token flow described above. The only difference is one extra +step when you connect. + +Follow the same **Configure access** steps to create a service account +(**Settings** → **Service Accounts**), grant it Maintainer access, and generate +a token from the service account's **Manage access tokens** with the `api`, +`read_api`, and `read_user` scopes. These are identical to GitLab.com. + +When you open the **Connect GitLab** modal in Hacktron, select **Self-hosted / +GitLab Enterprise** and enter your instance's base URL (e.g. +`https://gitlab.example.com`) before entering the token. + + + Self-hosted prerequisites: + - Your GitLab instance must be network-reachable from Hacktron. + - The service account's token must carry the `api`, `read_api`, and + `read_user` scopes on your self-hosted instance. + From 33c133f23b11c69896921a9ea60ece69491a0dfc Mon Sep 17 00:00:00 2001 From: maekuss Date: Thu, 11 Jun 2026 06:25:54 +0800 Subject: [PATCH 2/3] fix(docs): restore space in "Hacktron subscription" on People page Commit 362d294 accidentally deleted the space while documenting self-hosted GitLab support. Co-Authored-By: Claude Fable 5 --- code-review/people.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code-review/people.mdx b/code-review/people.mdx index 9e9d771..7b7d204 100644 --- a/code-review/people.mdx +++ b/code-review/people.mdx @@ -8,7 +8,7 @@ A developer needs a Code Review seat for Hacktron to review their pull requests ## Requirements -- An active free trial or paid Hacktronsubscription +- An active free trial or paid Hacktron subscription - A connected [Git provider integration](/platform/repositories) ## Auto-assign seats on PR From ecec283236d6527804c91d1a4667585a9b1bbdff Mon Sep 17 00:00:00 2001 From: maekuss Date: Thu, 11 Jun 2026 06:41:04 +0800 Subject: [PATCH 3/3] docs: clarify self-managed service account requirements for self-hosted GitLab Per current GitLab docs, service accounts on self-managed require EE and are admin-created by default (group Owners need an instance setting), so the flow is not identical to GitLab.com. Also document the valid-TLS and no-subpath prerequisites enforced by the connect flow. Co-Authored-By: Claude Fable 5 --- platform/repositories/gitlab.mdx | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/platform/repositories/gitlab.mdx b/platform/repositories/gitlab.mdx index 1a0d313..3ec4507 100644 --- a/platform/repositories/gitlab.mdx +++ b/platform/repositories/gitlab.mdx @@ -82,7 +82,15 @@ step when you connect. Follow the same **Configure access** steps to create a service account (**Settings** → **Service Accounts**), grant it Maintainer access, and generate a token from the service account's **Manage access tokens** with the `api`, -`read_api`, and `read_user` scopes. These are identical to GitLab.com. +`read_api`, and `read_user` scopes. + + + On self-managed GitLab, service accounts require GitLab EE, and by default + only an instance administrator can create them (administrators can also + allow top-level group Owners to create them). Alternatively, a personal + access token from any user with Maintainer access and the same scopes works + identically. + When you open the **Connect GitLab** modal in Hacktron, select **Self-hosted / GitLab Enterprise** and enter your instance's base URL (e.g. @@ -90,7 +98,10 @@ GitLab Enterprise** and enter your instance's base URL (e.g. Self-hosted prerequisites: - - Your GitLab instance must be network-reachable from Hacktron. - - The service account's token must carry the `api`, `read_api`, and - `read_user` scopes on your self-hosted instance. + - Your GitLab instance must be reachable from Hacktron over HTTPS with a + valid TLS certificate. + - GitLab installed under a URL subpath (e.g. `https://example.com/gitlab`) + is not supported — the base URL must be the instance origin. + - The token must carry the `api`, `read_api`, and `read_user` scopes on + your self-hosted instance.