Skip to content
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

misc: release script push tag #10193

Merged
merged 2 commits into from
Jan 9, 2020
Merged

Conversation

connorjclark
Copy link
Collaborator

couple items from #9857

@@ -17,7 +17,7 @@ fi

OLD_VERSION=$(node -e "console.log(require('./package.json').version)")
NEW_VERSION=$1
BRANCH_NAME="bump_$NEW_VERSION"
BRANCH_NAME="v$NEW_VERSION"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will this conflict with actual tags in any way? I always avoided naming my branch something that I plan to tag so it's always unambiguous but it could just be a git boogeyman I inherited

Copy link
Collaborator Author

@connorjclark connorjclark Jan 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nothing technical. just in your head :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nothing technical. just in your head :)

LIES!

➜  git-tag git init
Initialized empty Git repository
➜  git-tag git:(master) touch foo
➜  git-tag git:(master) ✗ git add -A
➜  git-tag git:(master) ✗ git commit -m 'foo'
[master (root-commit) 6079296] foo
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 foo
➜  git-tag git:(master) git checkout -b v1.0.0
Switched to a new branch 'v1.0.0'
➜  git-tag git:(v1.0.0) touch bar                                                                                                                                                                     ➜  git-tag git:(v1.0.0) ✗ git add -A
➜  git-tag git:(v1.0.0) ✗ git commit -m 'bar'
[v1.0.0 cd7d050] bar
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 bar
➜  git-tag git:(v1.0.0) git checkout master
Switched to branch 'master'
➜  git-tag git:(master) git tag -a v1.0.0 -m 'version tag'
➜  git-tag git:(master) touch baz
➜  git-tag git:(master) ✗ git add -A
➜  git-tag git:(master) ✗ git commit -m 'baz'
[master 0df3345] baz
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 baz
➜  git-tag git:(master) git checkout v1.0.0
warning: refname 'v1.0.0' is ambiguous.
Switched to branch 'v1.0.0'

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh no

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok i'll just do the other thing in this pr.

@connorjclark connorjclark changed the title misc: release script push tag, use vVERSION as branch name misc: release script push tag Jan 8, 2020
Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@patrickhulce patrickhulce merged commit 5e4b5fe into master Jan 9, 2020
@patrickhulce patrickhulce deleted the release-pushtag-and-branchname branch January 9, 2020 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants