You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For full context and reproducibility, see my repo for this issue. The bottom line is that docs descriptions:
true if branch protections or rulesets are configured for the ref that triggered the workflow run.
for the variables github.ref_protected and GITHUB_REF_PROTECTED, and their names, seem to imply that they should accurately reflect the protected state of a tag ref. However, at least in the context of GitHub Actions runs, they do not; rather they remain false in all cases for tags. The behavior and/or docs should be updated to better match each other.
Arguably, this bug belongs under API and Webhooks since that seems likely to be the root of the behavior, but I'm opening here since it's where the issue is presenting itself. Also, https://github.com/orgs/community/discussions/66588 is related, but not a bug report, so I'll just post a link to this on that discussion.
BugGitHub or a GitHub feature is not working as intendedActionsBuild, test, and automate your deployment pipeline with world-class CI/CD
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
GitHub Community
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Bug
Body
For full context and reproducibility, see my repo for this issue. The bottom line is that docs descriptions:
for the variables
github.ref_protectedandGITHUB_REF_PROTECTED, and their names, seem to imply that they should accurately reflect the protected state of a tag ref. However, at least in the context of GitHub Actions runs, they do not; rather they remainfalsein all cases for tags. The behavior and/or docs should be updated to better match each other.Arguably, this bug belongs under API and Webhooks since that seems likely to be the root of the behavior, but I'm opening here since it's where the issue is presenting itself. Also, https://github.com/orgs/community/discussions/66588 is related, but not a bug report, so I'll just post a link to this on that discussion.
All reactions