Branch protection rule uses tag when running release workflow

I’m creating a release workflow that pushes a commit to preprod and then prod environments.

I want these environments to only be accessible to commits on master which is protected by its own branch protection rules.

When I create a release from master the ref that the rule checks is the tag so 0.0.1 for example instead of master so fails the check. Is this something that could be updated?

I don’t really want to use a release branch and unfortunately I’m not able to do CD from master.

1 Like

Environment branch protection rules follow the same methodology of a branch protection Managing a branch protection rule - GitHub Docs

Unfortunately that’s our current limitation. We will work with branch refs.