problem deploy - action ref branch name

[LeonanRodrigues]

Select Topic Area

Bug

Body

Dear,

We are unable to carry out the deploy.
When we try we receive the following error:
"The branch "refs/heads/develop" is not allowed to deploy to develop due to environmental protection rules"

We noticed that the branch previously only appeared with the main name (develop, staging or master) and is now appearing with the full path (/refs/heads/$branch).

It is worth noting that nothing has changed on our side.
Can you help us?

[dcarvalhal]

I believe it may be related to the resolution of the previous incident.

[dcarvalhal]

https://www.githubstatus.com/incidents/00lscqwb6ht5

[dcarvalhal]

[LeonanRodrigues]

update

[LeonanRodrigues]

run: echo "branch=$(echo ${GITHUB_REF#refs/heads/})" >> $GITHUB_OUTPUT
id: extract_branch

[timcole]

We're currently experiencing the same issue. It worked a few hours ago but recently the branch is refs/heads/main instead of just main.

[gzt-fastradius]

We are seeing a similar issues. Our Github Action workflows aren't working because all pushes to main show up as refs/heads/main and therefore our workflow ignores it due to filtering we have in place.

[allwalte]

Same issue here, same timing (last couple of hours), and same presentation, with the branch seeming to read as refs/heads/main instead of just main and therefore failing protection rules. Also no changes on our end in that timeframe.

[ch4rms]

Broke all of our deploys

[ch4rms]

For now I have to disable all deployment protection, by disabling the protection we have on the repo managing GH via TF

[moloch--]

Same here

[ch4rms]

Related? https://github.blog/changelog/2023-09-13-github-actions-updates-to-github_ref-and-github-ref/

[allwalte]

That was very much my hunch as well; some sort of intended side effect or consequence?

[ch4rms]

If I select main on a workflow_dispatch style workflow, main is protected, and the environment protection is set to protected branches, it is blocked :(

[LeonanRodrigues]

Validate again guys, it looks like it's back to normal

@timcole @moloch-- @ch4rms @gzt-fastradius @allwalte

[Jeff-Dyck-SOF]

Yup, looks resolved, thanks. I've successfully deployed with Selected Branches set.

[ch4rms]

🤦‍♂️ Just removed env deploy protection on 50 repos....

[LeonanRodrigues]

@ch4rms back protection, man

[ch4rms]

Thanks @LeonanRodrigues for the follow up and tags!

[gzt-fastradius]

Yup, can confirm