Replies: 2 comments 1 reply
-
@d-fence second possible feature I'm not sure about: in #559 I added a note about "bump PRs" which would be merged into master after the freeze has been committed (to update the master version or whatever). Is that actually desirable / needed / useful / whatever? Would this have to be opt-in (the reverse of the release PRs) where it'd default to not doing anything, and if you need / want an initial post-fork update you can add one? |
Beta Was this translation helpful? Give feedback.
-
About the first idea: I prefer to keep the process coherent and create all the PR's manually and keep control of what will be merged. |
Beta Was this translation helpful? Give feedback.
-
@d-fence creating this to discuss / flesh out freeze wizard ideas which may not strictly speaking be issues, but could be proposals.
The first thing I was thinking about is: while freeze PRs are definitely necessary to update the code (otherwise the freeze-master would have to provide something crappy like a patch file), for "empty" commit maybe the freeze wizard could allow just entering the commit title, and would create an empty commit when it creates the branch?
This would make the freeze a tad less coherent, as the "empty" commits would be created immediately while the "code" commits would be merged thereafter, but it sounds like it should work (assuming the github API allows empty commits but I think it does)
Beta Was this translation helpful? Give feedback.
All reactions