You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
orcreate/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.
The text was updated successfully, but these errors were encountered: