Village Product and Developer Docs
  • 📘Welcome to Village Labs
    • Welcome to Village Labs
    • Self Service Onboarding
    • Help Pages
      • Adding and Deleting Users
      • Mapping Users to Source tool IDs
      • How to follow or unfollow other users
      • Configuring & Removing Daily Slack Notification Whitelist
      • Changing the Reporting Lines & Teams
      • Following Custom Reports
      • Google Drive Privacy: When will my documents appear in Village Reports?
    • Custom Reports
      • Creating Team Reports
      • Creating Custom Reports & Custom Prompt Library
    • Meetings
      • Connecting your Calendar
      • Configuring your Meetings
      • Meeting Summary Reports
    • Village Assistant
      • Github PR Review Tool
    • Security & Compliance
    • Data Privacy & Permissions
  • 🔌Data Connections
    • Airtable
    • Ashby
    • Clickup
      • Finding ClickUp User IDs
    • Figma
    • Github
      • Finding GitHub User IDs
    • Gitlab
    • Google - OAuth (Recommended)
    • Google - Manual Connection
    • Hubspot
    • Jira
      • Finding Jira User IDs
    • Confluence
      • Finding Confluence / Jira User IDs
    • Linear
    • Asana
    • Monday
    • Notion
    • Pipedrive
    • Slack
    • Basecamp
    • Zoom
  • 👩‍💻Legacy Developer Docs
    • Developer Quickstart
    • Village APIs: Introduction
      • Activity API
      • User Status API
      • Patch User API
      • Segments API
      • Redemption API
      • Master Award Controls
      • Connections (Referrals) APIs
      • GET APIs
    • 3rd Party Payments Integrations
    • Embedding Village Dashboards
  • 🕵️LEGACY Knowledge Base
    • Admin Quickstart
    • Referrals Support
    • The Basics of Village in 15 Minutes
    • Programs & Rules
      • Triggers
        • Activities
        • Goals
      • Conditions
        • Segment Conditions
        • Time Conditions
        • Max Budget Conditions
        • Conditional Multipliers
    • Awards
      • Monetary (Cash) Awards
      • Non-Monetary Awards
        • Funding
          • In-depth use cases for funding pools
      • Badges & Statuses
      • Award Expiration
    • Segments
      • Segmentation Use Cases
    • Rule Evaluation Logic Deep-dive
    • The Village Dashboards
      • Admin Account Creation
      • User Access Management
      • Network Settings
      • User Dashboard
    • BigQuery
    • Managing Payment Integrations
    • Referrals (Connections)
      • Pre-populating Users' Unique Referral Codes In Signup Flows & Forms
  • No and Low Code Solutions
    • No and Low Code Solutions
      • No & Low Code Solutions
  • Feedback
    • Village Docs Feedback Form
    • Feature Requests
    • Talk to our Team
Powered by GitBook
On this page
  • Prerequisites
  • Generating the credentials
  • Information required for the Village connection:

Was this helpful?

  1. Data Connections

Gitlab

How to connect your Github account with Village Labs.

PreviousFinding GitHub User IDsNextGoogle - OAuth (Recommended)

Last updated 7 months ago

Was this helpful?

Prerequisites

  • A Gitlab account with access to the repositories you wish to sync with Village Labs.

  • Depending on the configuration, either a Free or a Premium/Ultimate Gitlab plan

Generating the credentials

  1. Click 'Add new token'

  2. Do not enter an expiration date, as you'll need to reconnect once it expires. You can always revoke Village Labs' access to this token in future if required.

  3. Select the required scopes:

    api

  4. Next click 'Create personal access token' and copy / save your token.

Note: Village will only read, and not write data from your Gitlab instance. The only reason why an api, and not read_api scope is required is because, during the connection's setup, a webhook is configured to push real-time updates from Gitlab to Village's infrastructure.

Information required for the Village connection:

  • access_token: The access token created above

  • groups_list: Your group ID, or a a comma-separated (no spaces) list of the group ids which should be synchronized. This field is required and cannot be left blank.

    • This requires a Gitlab Premium/Ultimate/Self-managed instance

  • projects_list: A comma-separated (no spaces) list of the projects (or repositories) that should be synchronized. If left empty, Village will synchronize all projects that can be accessed (or within the groups configured above).

  • start_date: Date of the first record to synchronize, in the following format: 2024-01-01T00:00:00Z . Commits before this date will not be synchronized.

You can generate a personal access token at

Premium Tiers: If you wish to synchronize all repositories (projects) under a group (see config below), a Gitlab Premium/Ultimate/Self-managed instance is required: data will be (in part) synchronized through , which are not available in the Free Tier.

Free Tier: If you have a Free Tier Gitlab instance, you will need to provide an explicit list of the projects to synchronize: the data will be synchronized (in part) through .

🔌
https://gitlab.com/-/user_settings/personal_access_tokens
group hooks
project hooks
Personal access tokens | GitLab
Gitlab Personal Access Token Generation Tutorial
Logo