Skip to content

Core Services: 3.10 tracking issue

Created by: keegancsmith

Theme: What will break with 80k repositories across multiple code hosts?

Q4 Vision Statement: Sourcegraph operations are fast (e.g. search), instances scale to 80k repositories, private code is secure and respects ACLs for every authorization provider, and the product settings are easy to set up and understand for our largest customers.

Housekeeping

  • @rvantonder joins Core Services 🎉
  • @ryanslade joins Core Services Nov 4th 🎉
  • @keegancsmith out of office Nov 4th->15th

Required

@ryanslade we have assigned a task for you. Once you have joined and onboarded a bit we can change the task, this is a good initial task to try out but there may be something more appropriate. It is also under the "required" section. However, you will be onboarding so this can slip. We can also update this document with your real GitHub handle when appropriate :)

Polish

These are smaller tasks which anyone can do. They are all stretch tasks, with the main tasks being first priority.

Note: If the task is assigned to someone already, you can do it (please ping the person first).

  • On any change to external services, restart sync #6058 (closed)
  • Default symbol sidebar to using Zoekt for indexed branches #6078 (closed)
  • Single ctags docker image for both unindexed symbol svc and Zoekt #6080 (closed)
  • Verify sourcegraph.com falls back to non-indexed search when indexed pod is down #6057 (closed)
  • Rename Sourcegraph Go module to succinct name #4982
  • Drop recent_searches table/feature #6056 (closed)
  • Bitbucket Cloud repo syncing should allow hyphens in team names #6154 (closed)
  • Bitbucket Cloud external service doesn't provide "exclude" config option #6035 (closed)
  • Serious problems with external service auth provider config are never shown #6061 (closed)

3.9 tracking issue is #5710 (closed)