Difference between revisions of "GITHUB REF"
Line 5: | Line 5: | ||
GITHUB_REF: The branch or tag ref that triggered the workflow. For example, [[refs/heads/]]your-feature-branch-1 | GITHUB_REF: The branch or tag ref that triggered the workflow. For example, [[refs/heads/]]your-feature-branch-1 | ||
+ | |||
+ | Values: | ||
+ | git_[[branch]]=${GITHUB_REF#refs/heads/} | ||
+ | |||
Revision as of 20:29, 17 July 2023
https://docs.github.com/en/actions/learn-github-actions/environment-variables
The fully-formed ref of the branch or tag that triggered the workflow run. For workflows triggered by push, this is the branch or tag ref that was pushed. For workflows triggered by pull_request
, this is the pull request merge branch. For workflows triggered by release, this is the release tag created. For other triggers, this is the branch or tag ref that triggered the workflow run. This is only set if a branch or tag is available for the event type. The ref given is fully-formed, meaning that for branches the format is refs/heads/<branch_name>, for pull requests it is refs/pull/<pr_number>/merge, and for tags it is refs/tags/<tag_name>. For example, refs/heads/feature-branch-1.
GITHUB_REF: The branch or tag ref that triggered the workflow. For example, refs/heads/your-feature-branch-1
Values:
git_branch=${GITHUB_REF#refs/heads/}
Related
See also
- GitHub Actions,
act, .github/workflows/
,~/actions-runner/
,svc.sh
,deploy:, run:, runs-on:
,uses:
,steps:
,jobs:
,on:, env:, uses:, script:, continue-on-error:, template:, aws-actions, inputs:
,GITHUB_ENV, needs:, github.
, GitHub runner, my-docker-publish.yml, GitHub Actions variables, GitHub Actions contexts, GitHub Actions Importer, If:, SLSA, Actions Runner Controller (ARC),$GITHUB OUTPUT
,notify:
, Marketplace,GITHUB_TOKEN
Advertising: