Skip to content

Conversation

@DanielXiao
Copy link
Contributor

Adding tag from git command is different from tagging from
github web, the branch is refs/tags/* instead of releases/*
. Add refs/tags/* to branch so tag from git command can
also publish builds and trigger downstream project.

Fixes #

PR acceptance checklist:

[ ] All unit tests pass
[ ] All e2e tests pass
[ ] Unit test(s) included*
[ ] e2e test(s) included*
[ ] Screenshot attached and UX approved*

*if applicable, add n/a if not

Adding tag from git command is different from tagging from
github web, the branch is refs/tags/* instead of releases/*
. Add refs/tags/* to branch so tag from git command can
also publish builds and trigger downstream project.
@DanielXiao DanielXiao merged commit c36a2f8 into vmware:master Sep 12, 2018
@DanielXiao DanielXiao deleted the fix-release branch September 12, 2018 09:18
DanielXiao added a commit to DanielXiao/vic-ui that referenced this pull request Sep 12, 2018
Adding tag from git command is different from tagging from
github web, the branch is refs/tags/* instead of releases/*
. Add refs/tags/* to branch so tag from git command can
also publish builds and trigger downstream project.

(cherry picked from commit c36a2f8)
DanielXiao added a commit that referenced this pull request Sep 13, 2018
Adding tag from git command is different from tagging from
github web, the branch is refs/tags/* instead of releases/*
. Add refs/tags/* to branch so tag from git command can
also publish builds and trigger downstream project.

(cherry picked from commit c36a2f8)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants