Set up precise code intelligence with Sourcegraph

[chrismwendt]

Sourcegraph recently added support for precise code intelligence using LSIF, and we're looking for open source projects (such as Zoekt) to try it out!

With LSIF-based code intelligence and the Sourcegraph browser extension, you'll get hover tooltips on GitHub code views and PRs:

You can try it out on my fork before merging https://sourcegraph.com/github.com/chrismwendt/zoekt/-/blob/cmd/zoekt/main.go#L34:23

Without LSIF, you'll only see the default code intelligence, which is fuzzy and based on ctags + text search (in turn powered by Zoekt!).

All you need to do is:

• Generate a GitHub access token with public_repo scope at https://github.com/settings/tokens
• Create a new secret https://github.com/google/zoekt/settings/secrets called PUBLIC_REPO_GITHUB_TOKEN with that token
• Merge this PR

Every commit thereafter will trigger the LSIF action to generate and upload LSIF data for this repository to Sourcegraph.com. Anyone visiting https://sourcegraph.com/github.com/google/zoekt or viewing this repository with the Sourcegraph browser extension will then see precise code intelligence.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[hanwen]

can you point me to the ToS that govern this service?

[chrismwendt]

can you point me to the ToS that govern this service?

https://about.sourcegraph.com/terms

[hanwen]

sorry for the delays.

The old TOS for Sourcegraph ruffled some feathers in the past, so I'm trying to unruffle them.

[sqs]

@hanwen Thanks. If we can help unruffle anything, let me know (email works, too: [email protected]).