Skip to content

Core Services: 3.4 Tracking Issue

Created by: keegancsmith

Goals

  • All supported code hosts have moved to the new model of syncing repository metadata. This allows us to support detecting deletions and renames, avoiding expensive code host API requests on a user request path and solves many related repository metadata bugs.
  • A better model for repositoryPathPattern. Also known as aliases for repository names. This allows users to have more succinct names for repositories on their Sourcegraph instance. Additionally the use of the feature won't break the browser extension.
  • Onboard Thorsten.

Availability

  • @keegancsmith is out from 19th of April until the 26th.
  • @tsenart is out from the 15th of May until the 22nd.
  • @mrnugget is joining on the 23rd of April.

We are aiming for 17d person days of planned work. This is to account for responding to customer issues, vacation, helping other teams and onboarding Thorsten.

Planned Work

  • Integrate remaining code hosts with the new syncing model
  • RepoLookup should load metadata from database #3466 (closed) (@mrnugget)
  • Support new syncer in sourcegraph.com deployment #3459 (closed) (@mrnugget, @keegancsmith)
    • [ ] Add git repos to Sourcegraph.com #3457 (closed)
    • Sourcegraph.com does not auto add soft-deleted repositories. Will only be an issue once new syncer is enabled. #2933 (closed)
  • Remove syncer feature flag and delete old code paths #4000 (@tomas)
  • Repo name mappings are not universally supported #462 (closed) (@keegancsmith)
    • Impossible to change repositoryPathPattern after adding repositories #2741 (closed)
    • GitHub link disappears intermittently in 3.x #2677 (closed)
  • repos: Deprecate enabled/disabled state #3291 (closed) (@keegancsmith)

Stretch Goals

Onboarding @mrnugget

Note: We can adjust this plan based on Thorsten's preferences.

  • Week 1: Thorsten should spend first week getting to know people in SF and understanding the high level picture of Sourcegraph Inc. and sourcegraph/sourcegraph.

  • Week 2: Pair with us on whatever we are working on. Likely implementing a code host #3464 (closed) or #3465 (closed).

  • Week 3-4: Continue to learn how things are put together and begin taking on some of the planned work in the iteration or other important issues that can pop up.