Changesets without merge requests in Batch Changes
You can now create changesets in Batch Changes that push code directly to a branch, no merge request required.
You can now create changesets in Batch Changes that push code directly to a branch, no merge request required.
Sometimes you want to automate large-scale code changes without triggering a merge request, like updating internal tooling, modifying generated code, or experimenting with refactors. Until now, Batch Changes always assumed you wanted to open a merge request.
This update introduces a new type of changeset that doesn’t require a merge request. It simply:
The review state is always N/A, and the status is always OPEN, keeping things simple and efficient for low-touch workflows.
Learn more about changesets in our docs.