Ive currently disabled the branch protection that requires status checks to pass because it prevents the CI from tagging. I tried with adding an exception for the tagging user and also with the new GitHub rulesets feature, but that did not make any difference. It still ends up with:
remote: error: GH013: Repository rule violations found for refs/heads/develop.
remote: Review all repository rules at http://github.com/mxcube/mxcubecore/rules?ref=refs%2Fheads%2Fdevelop
remote:
remote: - Required status check "pre-commit" is expected.
remote:
To https://github.com/mxcube/mxcubecore
! [remote rejected] develop -> develop (push declined due to repository rule violations)
error: failed to push some refs to 'https://github.com/mxcube/mxcubecore'
Error: Process completed with exit code 1.
We have to find some other way to tag the release, maybe there are some other good ideas out there ?
Ive currently disabled the branch protection that requires status checks to pass because it prevents the CI from tagging. I tried with adding an exception for the tagging user and also with the new GitHub rulesets feature, but that did not make any difference. It still ends up with:
We have to find some other way to tag the release, maybe there are some other good ideas out there ?