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
However, the variable github.ref resolved to something like refs/heads/my_branch_name (as documented).
This causes the step to fail:
error: invalid tag "docker.pkg.github.com/bananer/my-repo/mps:refs/heads/my_branch_name": invalid reference format
Error: buildx call failed with: error: invalid tag "docker.pkg.github.com/bananer/my-repo/mps:refs/heads/my_branch_name": invalid reference format
Additional information
My goal is to publish to a docker tag matching my branch name, assuming this is also the intent of the example. Seems like there is no official way to get the branch name without refs/heads/ prefix in the official docs.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Thanks for opening an issue @bananer! I'll get this triaged for the team to take a look 👀
janiceilene
added
actions
This issue or pull request should be reviewed by the docs actions team
and removed
triage
Do not begin working on this issue until triaged by the team
labels
Jun 18, 2021
What article on docs.github.com is affected?
https://docs.github.com/en/actions/guides/publishing-docker-images#publishing-images-to-github-packages
What part(s) of the article would you like to see updated?
In the example file, the tag is specified like this:
However, the variable
github.ref
resolved to something likerefs/heads/my_branch_name
(as documented).This causes the step to fail:
Additional information
My goal is to publish to a docker tag matching my branch name, assuming this is also the intent of the example. Seems like there is no official way to get the branch name without
refs/heads/
prefix in the official docs.The text was updated successfully, but these errors were encountered: