<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=417142) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Sourcegraph has a feature "Batch Changes" whereby a user can automate large scale code changes. Currently sourcegraph are the only organisation offering this functionality and it would be a positive step forward and a further differentiator for GitLab to also offer this. Giving developers the ability to automate bulk code changes means that they become more efficient, reduce the hidden cost and burden of making updates and increases the speed of engineering. https://docs.sourcegraph.com/batch_changes/explanations/introduction_to_batch_changes https://about.sourcegraph.com/case-studies/indeed-accelerates-development-velocity If this were to be available directly from GitLab it would improve the customer experience and enhance their efficiency. This has been put forward by a large ~"GitLab Ultimate" customer and their SFDC link is below: https://gitlab.my.salesforce.com/0016100000K8E5P <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->