Enable Code Suggestions in GitLab 16.2 and earlier
Offering: Self-managed
To enable Code Suggestions on a self-managed instance for GitLab 16.1 or 16.2, follow these instructions.
Prerequisites:
- You must be an administrator.
- You must have a customer success manager.
- You must have a GitLab SaaS account. You do not need a Premium or Ultimate subscription.
- You must agree to the GitLab Testing Agreement.
- You must acknowledge that GitLab sends data from the instance, including personal data, to GitLab.com infrastructure.
Enable for your SaaS account
Start by enabling Code Suggestions for your GitLab SaaS account:
- Create a personal access token
with the
apiscope. - On the left sidebar, select your avatar.
- Select Preferences.
- In the Code Suggestions section, select Enable Code Suggestions.
- Select Save changes.
Enable for the instance
Then enable Code Suggestions for your self-managed GitLab instance:
- On the left sidebar, at the bottom, select Admin Area.
- Select Settings > General.
- Expand Code Suggestions and:
- Select Turn on Code Suggestions for this instance.
- In Personal access token, enter your GitLab SaaS personal access token.
- Select Save changes.
This setting is visible only in self-managed GitLab instances.
Request access
Finally, contact your customer success manager to request access. GitLab provisions access on a customer-by-customer basis for Code Suggestions on self-managed instances.
Your customer success manager then provisions access by commenting on issue 415393 (internal access only).
After GitLab has provisioned access to Code Suggestions for your instance, the users in your instance can now enable Code Suggestions.
Upgrade to GitLab 16.3
If you have a GitLab Free subscription and upgrade to GitLab 16.3 or later, to continue having early access to Code Suggestions, you must:
- Have a Premium or Ultimate subscription. These subscriptions support cloud licensing.
- Make sure you have the latest version of your IDE extension.
- Manually synchronize your subscription.