Site admin configuration for Batch Changes
Setup Batch Changes
-
Using Batch Changes requires a code host connection to a supported code host (currently GitHub, Bitbucket Server / Bitbucket Data Center, GitLab, and Bitbucket Cloud).
-
(Optional) Configure which users have access to Batch Changes Beta. By default, all users can create and view batch changes.
-
(Optional) Configure repository permissions, which Batch Changes will respect.
-
Setup incoming webhooks to make sure changesets sync fast. See Batch Changes effect on codehost rate limits.
-
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.