Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

go back to the previous branch after creating a PR

See original GitHub issue

After running shipjs prepare, user ends up on a branch like releases/vx.y.z. What if we checkout the previous (base) branch after creating the PR?

Ship.js checking out to a release branch is not so much clear to users, so it might confuse them.

(a) Should we add more message to clarify it? (b) or should we checkout the previous branch because there’s no(or less) reason to stay on the release branch?

Issue Analytics

State:
Created 4 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

2reactions

uetchycommented, Dec 24, 2019

Maybe something like that?

You are currently on releases/vX.X.X branch, the purpose of which is to make changes to release materials including CHANGELOG.md, and continue to prepare the next release. PR url here

Otherwise, you can safely check out another branch and get back to your development iteration.

0reactions

uetchycommented, Dec 24, 2019

@eunjae-lee yeah that’s a good idea to show command to checkout previous branch. I created PR #554 for this issue.