"Pending batch changes on this repo" badge
Created by: sourcegraph-bot
User Problem
-
Search users don't learn about Batch Changes in their context
-
Campaigns creators need to raise awareness on pending batch changes on downstream repositories through emails and internal communications to get them merged. Emails are painful, we should increase how much it's possible for repository owners to self-discover this.
Motivation
Batch Changes discoverability: Batch Changes's goal is to be accessible to every developer, and not only to a specialised team. It needs to be easy for all Sourcegraph users within a company to discover Batch Changes. Open batch changes are a good opportunity to raise awareness.
Looking at our most active customers per number of changesets merged, we observe that their number of MAUs is only ~ 2x their number of contributors.
Proposal
We want to contribute to raising awareness around batch changes, and creating incentives to merging batch changes changesets. We propose to:
-
include a "open batch changes on this repository" badge on each sourcegraph repository page
-
show the number of open batch change in the badge, and the number of merged Batch Changes
-
when users click on the badge, they go a new repository page, that shows the changesets (and which batch change they come from) on this repository,
-
from the batch change repository page, the user can take actions on the changeset, either by navigating to the codehost, or by selecting one or many changesets and trigger a bulk action.
-
on Sourcegraph.com, the badge points to the Batch Changes getting started page
Success criteria
In the spirit of having a limited number of pings, I don't think this is critical to measure in analytics.
A success criteria though is to observe an increase in the number of Batch Changes MAUs.