We would like to have the option to disable the back-propagation in the pipelines for static environments or have more options to control how the back-propagation should behave, like not running the PR validations for these types of Pull Requests.

When new changes reach the master branch, those changes should be pushed to the branch linked to a Salesforce environment. As it is today, the changes are back-propagated through new Pull Requests and because of the pipeline default config, the unit tests need to run which can block the sandboxes for some time depending on the complexity of the release that reached production. Then these PRs need to be monitored manually, causing unnecessary manual intervention and a bottleneck in high-demand pipelines.

By disabling the back-propagation through Pull Requests at this moment, we still have the option to sync the branches/environments through normal Deployment CI jobs, which we can automate.