Batch Changes

Make large-scale code changes across many repositories and code hosts

Create a batch change by specifying a search query to get a list of repositories and a script to run in each. You can also create a batch change on a monorepo by specifying which projects to run the script on. The batch change then lets you create changesets (a generic term for pull requests or merge requests) on all affected repositories or projects. Batch Changes allows you to track their progress until they're all merged. You can preview the changes and update them at any time. A batch change can also be used to track and manage manually created changesets.

Explanations

• Introduction to Batch Changes
• Permissions in Batch Changes
• Batch Changes design
• How src executes a batch spec
• Re-executing batch specs multiple times
• Running batch changes server-side

How-tos

• Creating a batch change
• Publishing changesets to the code host
• Updating a batch change
• Viewing batch changes
• Tracking existing changesets
• Closing or deleting a batch change
• Site admin configuration for Batch Changes
• Configuring credentials for Batch Changes
• Handling errored changesets
• Opting out of batch changes
• Bulk operations on changesets
• Using file mounts with server-side execution
• Batch changes in monorepos (Beta)
  • Creating changesets per project in monorepos
  • (Beta) Creating multiple changesets in large repositories

Tutorials

• Refactoring Go code using Comby
• Updating Go import statements using Comby
• Update base images in Dockerfiles
• Search and replace specific terms
• Examples repository

References

• Requirements
• Batch spec YAML reference
• Batch spec templating
• Batch spec cheat sheet
• Site admin configuration reference
• Troubleshooting
• FAQ
• CLI