GitLab settings (gitlab: )
GitLab is also a list, so multiple instances (e.g. gitlab.com plus a self-hosted instance) are supported side by side. The settings below cover connection and auth, which groups/projects/branches to include or exclude, performance tuning, and privacy controls.
Key
Required
Default
Description
instance_slug
Yes
-
Unique name for this instance
token
Yes (self-hosted)
-
GitLab Personal Access Token - must be a user PAT, not a group access token. Omit for Hivel-managed credentials - see Hivel-managed credentials below
url
No
https://gitlab.com
Override for self-hosted instances
earliest_data_date
Yes
-
YYYY-MM-DD
include_groups
No
all accessible
Group paths to sync
exclude_groups
No
-
Group paths to skip
include_projects
No
all
Project paths to sync
exclude_projects
No
-
Project paths to skip
extra_branches
No
-
Additional branches to fetch
concurrent_threads
No
5
Goroutines for concurrent project fetching
skip_ssl_verification
No
false
Disable TLS (self-signed certs on self-hosted)
exclude_commit_patterns
No
-
Glob patterns for commit messages to skip
exclude_pr_source_branches
No
-
Glob patterns for MR source branch
exclude_pr_target_branches
No
-
Glob patterns for MR target branch
exclude_file_paths
No
-
Glob patterns for file paths in MRs
redact_names_and_urls
No
false
Redact names and URLs
strip_text_content
No
false
Strip all text content
Multi-instance credentials - use a different ${ENV_VAR} per entry (same pattern as GitHub above):
Last updated