Site admin configuration for Batch Changes

Setup Batch Changes

1. Using Batch Changes requires a code host connection to a supported code host (currently GitHub, Bitbucket Server / Bitbucket Data Center, and GitLab).
2. (Optional) Configure repository permissions, which Batch Changes will respect.
3. Configure credentials.
4. Setup webhooks to make sure changesets sync fast. See Batch Changes effect on codehost rate limits.
   • GitHub
   • Bitbucket Server / Bitbucket Data Center
   • GitLab
5. Configure any desired optional features, such as:
   • Rollout windows, which control the rate at which Batch Changes will publish changesets on code hosts.
   • Forks, which push branches created by Batch Changes onto forks of the upstream repository instead than the repository itself.

Disable Batch Changes

• Disable Batch Changes.
• Disable Batch Changes for non-site-admin users.