-
Notifications
You must be signed in to change notification settings - Fork 116
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
Chore: Only reset to upstream/master for major/minor releases #750
Conversation
Verified that @pramodsum has signed the CLA. Thanks for the pull request! |
fi | ||
|
||
# Reset and fetch upstream with tags | ||
reset_tags || return 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you end up staying with this approach, I would log a message to the teminal saying what you did
build/release.sh
Outdated
@@ -44,6 +78,14 @@ increment_version() { | |||
# Old version | |||
OLD_VERSION=$(./build/current_version.sh) | |||
|
|||
# The master branch should not match the previous release tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't necessarily the master branch right? If we're coming from a patch this would be some detached state.
- This will prevent patch releases from resetting to upstream/master. Instead, it will reset to the previous version of Preview (if available). - See box/box-content-preview#750
- This will prevent patch releases from resetting to upstream/master. Instead, it will reset to the previous version of Preview (if available). - See box/box-content-preview#750
This will prevent patch releases from resetting to upstream/master. Instead, it will reset to the previous version of Preview (if available).
TODO: replicate the same logic in BoxAnnotations
Copy of #745