129 lines
5.3 KiB
Markdown
129 lines
5.3 KiB
Markdown
---
|
|
type: reference, how-to
|
|
---
|
|
|
|
# Sourcegraph integration
|
|
|
|
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16556) in GitLab 12.5. Please note that this integration is in BETA and [behind a feature flag](#enable-the-sourcegraph-feature-flag).
|
|
|
|
[Sourcegraph](https://sourcegraph.com) provides code intelligence features, natively integrated into the GitLab UI.
|
|
|
|
For GitLab.com users, see [Sourcegraph for GitLab.com](#sourcegraph-for-gitlabcom).
|
|
|
|
|
|
|
|
<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
|
|
For an overview, watch the video [Sourcegraph's new GitLab native integration](https://www.youtube.com/watch?v=LjVxkt4_sEA).
|
|
|
|
NOTE: **Note:**
|
|
This feature requires user opt-in. After Sourcegraph has been enabled for your GitLab instance,
|
|
you can choose to enable Sourcegraph [through your user preferences](#enable-sourcegraph-in-user-preferences).
|
|
|
|
## Set up for self-managed GitLab instances **(CORE ONLY)**
|
|
|
|
Before you can enable Sourcegraph code intelligence in GitLab you will need to:
|
|
|
|
- Enable the `sourcegraph` feature flag for your GitLab instance.
|
|
- Configure a Sourcegraph instance with your GitLab instance as an external service.
|
|
|
|
### Enable the Sourcegraph feature flag
|
|
|
|
NOTE: **Note:**
|
|
If you are running a self-managed instance, the Sourcegraph integration will not be available
|
|
unless the feature flag `sourcegraph` is enabled. This can be done from the Rails console
|
|
by instance administrators.
|
|
|
|
Use these commands to start the Rails console:
|
|
|
|
```shell
|
|
# Omnibus GitLab
|
|
gitlab-rails console
|
|
|
|
# Installation from source
|
|
cd /home/git/gitlab
|
|
sudo -u git -H bin/rails console RAILS_ENV=production
|
|
```
|
|
|
|
Then run the following command to enable the feature flag:
|
|
|
|
```
|
|
Feature.enable(:sourcegraph)
|
|
```
|
|
|
|
You can also enable the feature flag only for specific projects with:
|
|
|
|
```
|
|
Feature.enable(:sourcegraph, Project.find_by_full_path('my_group/my_project'))
|
|
```
|
|
|
|
### Set up a self-managed Sourcegraph instance
|
|
|
|
If you are new to Sourcegraph, head over to the [Sourcegraph installation documentation](https://docs.sourcegraph.com/admin) and get your instance up and running.
|
|
|
|
### Connect your Sourcegraph instance to your GitLab instance
|
|
|
|
1. Navigate to the site admin area in Sourcegraph.
|
|
1. [Configure your GitLab external service](https://docs.sourcegraph.com/admin/external_service/gitlab).
|
|
You can skip this step if you already have your GitLab repositories searchable in Sourcegraph.
|
|
1. Validate that you can search your repositories from GitLab in your Sourcegraph instance by running a test query.
|
|
1. Add your GitLab instance URL to the [`corsOrigin` setting](https://docs.sourcegraph.com/admin/config/site_config#corsOrigin) in your site configuration.
|
|
|
|
### Configure your GitLab instance with Sourcegraph
|
|
|
|
1. In GitLab, go to **Admin Area > Settings > Integrations**.
|
|
1. Expand the **Sourcegraph** configuration section.
|
|
1. Check **Enable Sourcegraph**.
|
|
1. Set the Sourcegraph URL to your Sourcegraph instance, e.g., `https://sourcegraph.example.com`.
|
|
|
|
|
|
|
|
## Enable Sourcegraph in user preferences
|
|
|
|
If a GitLab administrator has enabled Sourcegraph, you can enable this feature in your user preferences.
|
|
|
|
1. In GitLab, click your avatar in the top-right corner, then click **Settings**. On the left-hand nav, click **Preferences**.
|
|
1. Under **Integrations**, find the **Sourcegraph** section.
|
|
1. Check **Enable Sourcegraph**.
|
|
|
|
|
|
|
|
## Using Sourcegraph code intelligence
|
|
|
|
Once enabled, participating projects will have a code intelligence popover available in
|
|
the following code views:
|
|
|
|
- Merge request diffs
|
|
- Commit view
|
|
- File view
|
|
|
|
When visiting one of these views, you can now hover over a code reference to see a popover with:
|
|
|
|
- Details on how this reference was defined.
|
|
- **Go to definition**, which navigates to the line of code where this reference was defined.
|
|
- **Find references**, which navigates to the configured Sourcegraph instance, showing a list of references to the highlighted code.
|
|
|
|
|
|
|
|
## Sourcegraph for GitLab.com
|
|
|
|
Sourcegraph powered code intelligence will be incrementally rolled out on GitLab.com.
|
|
It will eventually become available for all public projects, but for now, it is only
|
|
available for some specific projects within the [`gitlab-org`](https://gitlab.com/gitlab-org/)
|
|
group, e.g., <https://gitlab.com/gitlab-org/gitlab>. This means that you can see
|
|
it working and use it to dig into the code of these projects, but you cannot use
|
|
it on your own project on GitLab.com yet.
|
|
|
|
If you would like to use it in your own projects as of GitLab 12.5, you can do so by
|
|
setting up a self-managed GitLab instance.
|
|
|
|
Follow the epic [&2201](https://gitlab.com/groups/gitlab-org/-/epics/2201) for
|
|
updates.
|
|
|
|
## Sourcegraph and Privacy
|
|
|
|
From Sourcegraph's [extension documentation](https://docs.sourcegraph.com/integration/browser_extension#privacy) which is the
|
|
engine behind the native GitLab integration:
|
|
|
|
> Sourcegraph integrations never send any logs, pings, usage statistics, or telemetry to Sourcegraph.com.
|
|
> They will only connect to Sourcegraph.com as required to provide code intelligence or other functionality on public code.
|
|
> As a result, no private code, private repository names, usernames, or any other specific data is sent to Sourcegraph.com.
|