This is a compilation of some common questions about Batch Changes.
What happens if my batch change creation breaks down at 900 changesets out of 1,000? Do I have to re-run it all again?
Batch Changes’ default behavior is to stop if creating the diff on a repo errors. You can choose to ignore errors instead by adding the
-skip-errors flag to the
src batch preview command.
Can we close a batch change and still leave the changesets open?
Yes. There is a confirmation page that shows you all the actions that will occur on the various changesets in the batch change after you close it. Open changesets will be marked ‘Kept open’, which means that batch change won’t alter them. See closing a batch change.
How scalable are Batch Changes? How many changesets can I create?
Batch Changes can create tens of thousands of changesets. This is something we run testing on internally. Known limitations:
- Since diffs are created locally by running a docker container, performance depends on the capacity of your machine. See How
srcexecutes a batch spec.
- Manipulating (commenting, notifying users, etc) changesets at that scale can be clumsy. This is a major area of work for future releases.
My batch change does not open changesets on all the repositories it should. Why?
Do you have enough permissions? Batch Changes will error on the repositories you don’t have access to. See Repository permissions for Batch Changes.
repositoriesMatchingQuerycontain all the necessary flags? If you copied the query from the sourcegraph UI, note that some flags are represented as buttons (case sensitivity, regex, structural search), and do not appear in the query unless the experimental
copyQueryButtonfeature toggle is enabled.
Can I create tickets or issues along with Batch Changes?
What happens to the preview page if the batch spec is not applied?
Unapplied batch specs are removed from the database after 7 days.