cabal
cabal copied to clipboard
Expose BuildFlags and ClientHaddockFlags
This will fix #8351
Please include the following checklist in your PR:
- [x] Patches conform to the coding conventions.
- [x] Any changes that could be relevant to users have been recorded in the changelog.
- [x] The documentation has been updated, if necessary.
FYI: CI is borked right now (#8356), so the error probably has nothing to do with this PR.
Let me rebase to see if the recent CI workaround unblocks your testing.
@mergify rebase
rebase
✅ Branch has been successfully rebased
This might be ready in my mind.
Splendid. Let's wait for the mandatory second review.
Someone has to apply the squash+merge_me label now.
@kokobd: I've granted you Triage authorization so that you can set the squash+merge_me (or merge_me) label on this PR and behold the mergifyIO magic (which takes 2 todays to unfold, in order to give people time to comment).
CI seems to be broken. Let me rebase to verify if our recent partial fixes help.
@mergify rebase
rebase
✅ Branch has been successfully rebased
what a strange error:

what a strange error:
Yes, I think something broke in our CI infrastructure. Due to that mergify can't merge automatically, so let me merge manually.
@mergify rebase
rebase
☑️ Nothing to do
- [X]
-closed[:pushpin: rebase requirement] - [ ] any of:
- [ ]
#commits-behind>0[:pushpin: rebase requirement] - [ ]
-linear-history[:pushpin: rebase requirement]
- [ ]
@kokobd: thank you!
backport 3.8
✅ Backports have been created
- #8468 Expose BuildFlags and ClientHaddockFlags (backport #8353) has been created for branch
3.8