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

💡Improve conditional release process #268

Open
brody4hire opened this issue Mar 27, 2020 · 0 comments
Open

💡Improve conditional release process #268

brody4hire opened this issue Mar 27, 2020 · 0 comments

Comments

@brody4hire
Copy link

This thread on [email protected] led to a discussion with @erisu about the number of extra commits that would persist in master in case of a failed release.

A simple solution could be to use a special tag format such as create/7.0.1 or create/2020.03.27/7.0.1 that we would use to build the npm package, and then just push the package build tag to GitHub. Then we should be able to abandon or delete it if we find a problem during the vote. I am thinking that a lot of the needed git and GitHub functionality should work with this build tag idea.

It would also be possible to make a PR or draft PR when making a release, which could be closed and abandoned if needed.

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

No branches or pull requests

1 participant