Deploy to Environments only from Tag

[gopisaba]

Select Topic Area

Bug

Body

We have Selected Deployment Branches with the regex pattern v[0-9]+.[0-9]+.[0-9]+ for the Github Environments to allow deployments only from the tags but it stopped working recently on all the repositories. Is there any changes on the Github side to make this stop working?

Error Message
Branch "v3.5.0" is not allowed to deploy to env1 due to environment protection rules.

[nirav-gajera]

• Go to the environment settings page.
• Click on the Deployment protection rules tab.
• In the Allowed tags section, add the tags that you want to allow deployments from.
• Click on the Save button.
  Once you have updated your deployment branches regex pattern or allowed specific tags, you should be able to deploy from tags again.

[gopisaba]

Sorry! can't find anything like Allowed tags section under Deployment protection rules tab in Environment settings page.

I set the regex pattern in Deployment branches for the tags but that is no longer missing. What am I missing?

[javierlga]

You can't use the + quantifier, it sucks but GitHub environment protection uses fnmatch from Ruby, reference: docs, so testing this:

puts File.fnmatch('v[0-9]+.[0-9]+.[0-9]+', 'v3.5.0')

will always return false. Using a wildcard instead as puts File.fnmatch('v[0-9]*.[0-9]*.[0-9]*', 'v3.5.0') will work but it's not super restrictive, as someone could create a tag as the following v3test.5test.0test and still be able to deploy, it's a shame it doesn't support the same filter pattern as GitHub actions workflows.

[sassman]

hope that GitHub at least adds a small help text above the field to elaborate on this counter intuitive detail.