Just to clarify: the old (current) stable should be called (ie renamed) stable_30?
Yeah that was my idea. Because if we call it stable_old then we cannot do it another time when 3.2 is out and we sync again.
The new branch should be called “stable” of course.
1 Like
Done.
stable renamed to stable_30
and now there is a new stable identical to main.
3 Likes
Hi @development_team It appears I don’t have the necessary permissions to make the stable branch protected. Could you please apply the appropriate protection rules to the branch if needed? Thank you!
1 Like
I’ve made you an admin for the Custom Wizard repo.
2 Likes