Is there an existing issue for this?
Problem summary
Despite doing a PR, semantic-release creates one little commit updating the verison of pyproject.toml and the CHANGELOG.md. As a result, the original branch protection requiring a PR don't apply anymore because that is run on the commit AFTER the PR.
As a result, we need to sort out this entire CI/CD workflow.
Code for reproduction
Does not apply. Happens on each CI/CD workflow run
Actual outcome
No release worklow, publish-to-pypi does not run
Error messages
remote: error: GH013: Repository rule violations found for refs/heads/main.
remote: Review all repository rules at https://github.com/AustralianCancerDataNetwork/omop-graph/rules?ref=refs%2Fheads%2Fmain
remote:
remote: - Changes must be made through a pull request.
remote:
To https://github.com/AustralianCancerDataNetwork/omop-graph
Expected outcome
semantic-release and entire workflow run as expected yet the main branch still is protected.
System info
Is there an existing issue for this?
Problem summary
Despite doing a PR,
semantic-releasecreates one little commit updating the verison ofpyproject.tomland theCHANGELOG.md. As a result, the original branch protection requiring a PR don't apply anymore because that is run on the commit AFTER the PR.As a result, we need to sort out this entire CI/CD workflow.
Code for reproduction
Actual outcome
No release worklow,
publish-to-pypidoes not runError messages
Expected outcome
semantic-releaseand entire workflow run as expected yet the main branch still is protected.System info