Closed IanEdington closed 1 year ago
This looks reasonable, but the main reason for using main-beta and main-alpha is that main* are protected branches. Do we have the protection setup for alpha and beta before merging this?
I simplified the rules quite a bit:
main-v4
, main
or main-v2
IMO)The workflow would be. Make a change, put up a PR, get it approved & merged. If you want to deploy to alpha or beta, force push to those branches.
As I'm writing this out though I wonder if it would be better to remove 'alpha' and 'beta' in favour of targeting main-v4
, main
or main-v2
. The package.json config should allow all three 'main' branches to be released to their correct channels.
I'm going to close this for now since I haven't been able to dedicate time towards it. I'll re-open in the future when we start working on it again
The tags on npm have
main
in the currently. By usingalpha
andbeta
as the branch names this should remove the "main" from the names