This section is about Batch Changes, which helps you automate and ship large-scale code changes across many repositories and code hosts.
Batch Changes helps you ship large-scale code changes across many repositories and code hosts. You can create pull requests on all affected repositories, and it tracks their progress until they're all merged. You can also preview the changes and update them at any time.
Get Started Key ConceptsAs you learn about Batch Changes, it's helpful to understand the following terms:
Term Description batch-change A group of related changes to code, along with a title and description batch-spec A YAML file that defines a batch change, including target repositories, commands to execute, and templates for changesets and commits. It represents your high-level intent, like "linting files in repositories with apackage.json file" changesets Refers to associated pull requests, merge requests, or any reviewable code segments linked to a batch change published-changeset A published changeset is a commit, branch, and changeset that has been created on the code host. An unpublished changeset is a preview visible in the batch change but not yet existing on the code host spec A spec is a record of intent for batch changes or changesets. It guides the system to align the actual outcomes with your specified intent continuously changeset-spec A batch change has many changeset specs, which are produced by executing the batch spec (i.e., running the commands on each selected repository) and then using its changeset template to produce a list of changesets, including the diffs, commit messages, changeset title, and changeset body batch-changes-controller The batch change controller reconciles the actual state of the batch change's changesets on the code host to match your desired intent (as described in the changeset specs) Create a Batch Change
To create a batch change, use Code Search to run a search query to find all occurrences of code to change and make every change with a single declarative spec file.
A batch change then tracks all of its changesets (a generic term for pull requests or merge requests) for updates to:
You can see the overall trend of a batch change in the burndown chart, which shows the proportion of changesets that have been merged over time since the batch change was created.
You can also create a batch change on a monorepo by specifying which projects to run the script on. A batch change can also be used to track and manage manually created changesets.
Supported code hosts and changeset typesA single batch change can span many repositories and many code hosts. The generic term changeset is used to refer to any of the following:
You can use Batch Changes to make the following kinds of changes:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4