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

Update documentation about double-release bug #42

Open
joshdevins opened this issue Jan 19, 2018 · 0 comments
Open

Update documentation about double-release bug #42

joshdevins opened this issue Jan 19, 2018 · 0 comments
Labels
Milestone

Comments

@joshdevins
Copy link
Collaborator

joshdevins commented Jan 19, 2018

When performing a release, since we cross-compile, the first "push changes to repo" should be the only ones. The second time you get asked to tag and push to remote, you should choose to NOT do it since they versions are already updated. Furthermore, you should always make sure to specify the same release version, you will be asked twice (again, once per cross-compile version).

@joshdevins joshdevins added the bug label Jan 19, 2018
@joshdevins joshdevins added this to the 1.1.0 milestone Jan 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant