-
Notifications
You must be signed in to change notification settings - Fork 698
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
Changelogs 3.14 #10336
Changelogs 3.14 #10336
Conversation
Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Uh, why was the merge label set before it was ready to merge? |
Do we want to quickly do a PR reverting this and re-commit when it's ready, or force-push it away since nobody should be using 3.14 yet? |
This reverts commit 7ee3d54.
There doesn't appear to be a way to reopen a merged PR, even for an admin. |
Sorry, I jumped the gun with the label. I'll open another PR applying the suggestions. |
The problem with that is some of those wanted discussion, I think — and that discussion will be lost. Unfortunately, there doesn't seem to be a way around this. |
While checking for changes in the PR won't catch comments, they should actually be available and it should be possible to craft Mergify rules for them. I'll need to set up a test repo and play around with it to see what actually works. Unfortunately, between life and the amount of time I've been spending in doctors' offices of late (which has made the life issues worse), this will probably take some time. |
Yes, but nothing says we can't continue discussions on the new PR. It's not optimal but it's certainly doable. |
* changelogs for Cabal-3.14 and (incomplete) cabal-install-3.16 * cleanup changelog-d files afer creating the 3.14 changelog * Apply suggestions from geekosaur Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com> * Apply more suggestions from geekosaur * Apply suggestions from geekosaur (contd.) Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com> --------- Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
* changelogs for Cabal-3.14 and (incomplete) cabal-install-3.16 * cleanup changelog-d files afer creating the 3.14 changelog * Apply suggestions from geekosaur Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com> * Apply more suggestions from geekosaur * Apply suggestions from geekosaur (contd.) Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com> --------- Co-authored-by: brandon s allbery kf8nh <allbery.b@gmail.com>
Forward port of haskell#10336 and haskell#10338
Forward port of haskell#10336, haskell#10338, and haskell#10358
So for the record, we were missing a branch protection rule requiring that all review comments be resolved before merging. |
Forward port of haskell#10336, haskell#10338, and haskell#10358
Previous attempt : #10323
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: