Skip to content

Import changesets in a few clicks

Created by: sourcegraph-bot

Motivation

  • Customers tell us that tracking and managing changesets with the GUI is extremely useful
  • We think that this is a great, low-effort entrypoint to get users into the product and help them discover batch changes.
  • In practice I see 0 imported changesets vs  ~ 600 published changesets over the 5 last weekly cohorts.
  • This does not require any server side batch changes backend, so we could use it to validate the Server Side Batch Changes GUI independently of the backend.

User Problem

Assumption ✅ : importing changesets has a lot of value and looks great when shown, but is hard to do in practice as it requires listing the PRs one by one in a spec file.

Use cases:

  • I want to import changesets that I manually opened so as to track the progress of a change I'm making across multiple teams.
  • I want top import everything dependabot opened into a Batch Change dashboard (+3)

Ideas

  • Create imported Batch Changes by creating a spec and running it in the GUI (no Docker run needed)
  • A GUI view to add search, filter and pick changesets to add.
  • Even better, monitor GitHub (via org-wide webhooks) for any PRs with a label campaign:whatever/whatever and adds them to that campaign.
  • the gh CLI might have some nice options that would let you do something like gh pr list -whatever | xargs gh pr update label=campaign:whatever/whatever. It does not support searching by branch name though.
  • Add changesets from branches returned by a Sourcegraph search query. Eg. rev:this/branch/name. Could be useful for example to bring dependabot updates into Batch Changes, as they use standard branch names.
  • Build a Sourcegraph extension. Users can use codehost filtering UI to send changests to Sourcegraph.