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, GitLab, and Bitbucket Cloud).

  2. (Optional) Configure which users have access to Batch Changes Beta. By default, all users can create and view batch changes, but only the batch change's author or a site admin can administer a given batch change.

    • Additionally, you can also customize org settings to allow members of an organization to share administration privileges over batch changes created in that organization.
  3. (Optional) Configure repository permissions, which Batch Changes will respect.

  4. Configure credentials.

  5. Setup incoming webhooks to make sure changesets sync fast. See Batch Changes effect on codehost rate limits.

  6. 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.
    • Outgoing webhooks, which publish events related to batch changes and changesets to enable deeper integrations with your other tools and systems.
    • Auto-delete branch on merge/close, which automatically deletes branches created by Batch Changes when changesets are merged or closed.
    • Commit signing for GitHub, which signs commits created by Batch Changes via a GitHub App Beta.

Disable Batch Changes