Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

fix(version-info): explicitly specify the remote #6678

Closed
wants to merge 1 commit into from

Conversation

chirayuk
Copy link
Contributor

git ls-remote --tags assumes that you have a remote set up for your
current branch. That isn't the case, at least for me, when I'm working
on local branches. grunt write doesn't do the right thing in that
case (git ls-remote --tags bails out and the silent: true param makes
this a pain to debug.) Prefer explicit to implicit.

@mary-poppins
Copy link

Love it, Chirayu! ❤️

`git ls-remote --tags` assumes that you have a remote set up for your
current branch.  That isn't the case, at least for me, when I'm working
on local branches.  `grunt write` doesn't do the right thing in that
case (`git ls-remote --tags` bails out and the silent: true param makes
this a pain to debug.)  Prefer explicit to implicit.
@btford btford added this to the 1.3.0-beta.3 milestone Mar 17, 2014
@chirayuk chirayuk added cla: yes and removed cla: no labels Mar 18, 2014
@petebacondarwin
Copy link
Contributor

LGTM. Let's merge this.

@chirayuk chirayuk closed this in 0c930a1 Mar 20, 2014
@tbosch
Copy link
Contributor

tbosch commented Mar 20, 2014

Thanks!

chirayuk added a commit that referenced this pull request Mar 20, 2014
`git ls-remote --tags` assumes that you have a remote set up for your
current branch.  That isn't the case, at least for me, when I'm working
on local branches.  `grunt write` doesn't do the right thing in that
case (`git ls-remote --tags` bails out and the silent: true param makes
this a pain to debug.)  Prefer explicit to implicit.

Closes #6678.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants