PR review "final report box" to show before merging

[fregante]

When about to merge PRs:

we could show a final "report" box listing what's about to happen:

• full list of commits that will be merged/squashed/rebased, as suggested in Clear PR merge commit description field #2564 (comment)
• issues/PRs that will automatically be closed (via closes #11 keyword) or if none will be closed
• any potential issues to be aware of:
  • unrebased !squash/!fixup commits: Warn before merging a PR if it contains fixup or squash commits #2385
  • reviews that haven't been resolved
  • CI that hasn't completed or passed
• TODOs added by the PR Highlight TODO and FIXME. #2634

What else could this include?

[fregante]

full list of commits that will be merged/squashed/rebased

This would be a good start for this feature

[fregante]

• issues/PRs that will automatically be closed (via closes #11 keyword) or if none will be closed

Actually I'd like to see this more. Sometimes new users forget to mark "closes X" correctly so it'd be good to see "No issues will be closed when merging this PR" as well as "X Y and Z will be closed after merging.

[rkrisztian]

I need the warnings or even merge checks for !squash and !fixup commits the most. I'm concerned that https://github.com/13rac1/block-fixup-merge-action still does not support merge queues, already has deprecation warnings and it has not received updates since 2021.

Edit: Plus I think it would be more ideal if it wasn't a GitHub Action that needed to check for such commits. It doesn't feel right if an action checks this. Commits are metadata, it's not really the responsibility of a pipeline execution to deal with them. A PR pipeline typically executes some build and tests, and if the check for commits is implemented wrongly, it won't be a separate check but will fail the PR pipeline prematurely just because there's a fixup commit that will be squashed once everything is ready for merge.

[cooljeanius]

I'm concerned that 13rac1/block-fixup-merge-action still does not support merge queues

I mean, support for merge queues isn't really that widespread in general; see also #6850