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

Bug: undefined branch name #137

Closed
blakedietz opened this issue Apr 23, 2019 · 3 comments
Closed

Bug: undefined branch name #137

blakedietz opened this issue Apr 23, 2019 · 3 comments
Labels

Comments

@blakedietz
Copy link

blakedietz commented Apr 23, 2019

Log

Config

https://github.com/blakedietz/vscode-nested-tags/blob/master/package.json#L96

https://github.com/blakedietz/vscode-nested-tags/blob/master/package.json#L131

What happened

For some reason my semantic release user is able to release, but the branch it's deploying to is master.

https://github.com/blakedietz/vscode-nested-tags/tree/undefined

What did you expect to happen

I expected that my changelog file was to be published to master instead of "undefined".

@pvdlg
Copy link
Member

pvdlg commented Jun 5, 2019

Can you provide the logs of the problematic run?

@vadimsgaliskins
Copy link

@blakedietz you seem to have beta version of semantic-release package
https://github.com/blakedietz/vscode-nested-tags/blob/master/package.json#L46
but stable version of @semantic-release/git plugin
https://github.com/blakedietz/vscode-nested-tags/blob/master/package.json#L32

Switching to beta release of @semantic-release/git helped me solve this exact issue in my workflow.

@pvdlg
Copy link
Member

pvdlg commented Jun 13, 2019

The version discrepancy pointed out by @blakedietz is most likely the cause of this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants