-
Notifications
You must be signed in to change notification settings - Fork 59.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Actions: Be precise about the format #400
Conversation
I stumbled across this to add the plain branch name to the [Docker push action](https://github.com/docker/build-push-action) as a tag, which does not work with ```yaml with: tags: tillepille/my-image: ${{ github.ref }} ```
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Thanks for opening a PR 👍 Please fill out the pull request template in the top comment in this pull request, then we'll get this up for review! |
@janiceilene Sorry, I missed it when opening the mr via whole UI workflow. Filled out, Issue also created |
Thanks so much for filling out the template and opening an issue @tillepille 💛 I'll get this triaged for review! |
content/actions/reference/context-and-expression-syntax-for-github-actions.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. |
I stumbled across this to add the plain branch name to the Docker push action as a tag, which does not work with
Why:
I tried to get the plain branch name as a variable in my Action. The documentation suggested to me that this is the plain branch name e.g.
master
but it is in the format ofrefs/heads/master
which isn't applicable as e.g a docker tag.What's being changed:
Be more precise about the format of the variable.
I added in the form of
refs/heads/<BRANCH_NAME>
to the explanation.Check off the following:
closes #476