Skip to content

fix: semantic-release and sort out main branch protection #14

Description

@nicoloesch

Is there an existing issue for this?

  • I have searched the existing issues

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

Not applicable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions