Três contos de amor

Sourcegraph ❤️ Open Source

(or, as I like to call it, GNU/Sourcegraph)

Proposal

We open Batch Changes up (with limits!) on sourcegraph.com to be applied to repos with open source licences.

Benefits

  • Marketing
  • Recipes
  • Discovering new use cases

Requirements

  • Executor deployment on cloud
  • Billing
  • Usage limits, including a fair use policy
  • Monitoring

Risks

  • Cost
  • Crypto miners
  • Harassment

(that was)

Sourcegraph ❤️ Open Source

(because every maintainer wants more pull requests, right?)

Batch Changes ❤️ JIRA

(don't worry, I'm confused too)

Custom changesets

What if you could add changesets to batch changes via an API, and manage them externally?

Why?

This gives you a single pane of glass to bring in issues from a tracking system, or really anything you want.

How?

  • API to add and update changesets within a batch change.
  • No reconciler operations; pure syncing via a user-provided callback to get the status, plus whatever updates they want to push outside of polling.
  • Probably requires custom metadata in batch specs to allow webhooks to trigger adding changesets in the first place.

(that was)

Batch Changes ❤️ JIRA

(that sound you hear is developers crying out in pain)

Notebooks ❤️ Batch Changes

(together at last)

(that was)

Notebooks ❤️ Batch Changes

(but not spiral bound notebooks, because they're terrible for left handed people)