-
Notifications
You must be signed in to change notification settings - Fork 202
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
versionBranches fails on new major if branch does not exist #1270
Comments
I pushed a |
I'll take a look at this later today! |
Googling for this error mentions a lot of instances of the branch not matching a remote, but I am fairly certain we have that right. We run
To my knowledge, at the time this runs, we are on |
Yeah it should be run from baseBranch. I think I found the bug. PR incoming! |
🚀 Issue was released in |
Describe the bug
I have
versionBranches: true
set in my auto config, and expect newMAJOR
-labeled releases to create a branch to track the new release line.To Reproduce
.autorc.js
MAJOR
intomaster
npx auto
Expected behavior
auto
creates a new branch to track the major version lineEnvironment information:
Additional context
snippet
The text was updated successfully, but these errors were encountered: