With branch protection rules, when there are required checks for merging into dev:
The release workflow will not be able to fast-forward main->dev to bring the release tag into the main branch, and a PR like #91 will be opened instead.
Notably, eventhough we allow an automation user to bypass a pull request
For now, I've disabled the required checks on dev so that the automation will work in the future, but I disallowed everyone, except the automation user, from pushing to dev.
With branch protection rules, when there are required checks for merging into![image](https://github.com/ACCESS-Cloud-Based-InSAR/dem-stitcher/assets/7882693/c3c69cb7-3f39-4785-b096-63c3ca2063d2)
dev
:The release workflow will not be able to fast-forward main->dev to bring the release tag into the main branch, and a PR like #91 will be opened instead.
Notably, eventhough we allow an automation user to bypass a pull request![image](https://github.com/ACCESS-Cloud-Based-InSAR/dem-stitcher/assets/7882693/e5d0c1f2-a992-4be3-b22b-569023065ce0)
this has no effect on required status checks: https://github.com/orgs/community/discussions/43460)
Rulesets allows more fine-grained control and would allow teams to bypass required status checks: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#about-rulesets