- From: Matt Giuca <notifications@github.com>
- Date: Sun, 23 Apr 2023 21:24:28 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/1075@github.com>
Spinning off from #1069. @marcoscaceres did you change a setting here or is GitHub forcing this upon us? (I think I used to be an admin but I don't appear to be any more... I can access some Settings but most are hidden from me.) This is what I see on the submit button for an approved PR:  The drop-down has no other options. I don't recall seeing this before; I was previously given a choice to squash or merge. In Settings, it still seems to be set up that way, so I'm not sure what's changed or why it's forcing us to use Merge Queue (I don't even see an option for Merge Queue):  The problem with Merge Queue is that there [doesn't appear to be any way to set the commit message](https://github.com/orgs/community/discussions/15925). I don't know what the default message is, but it probably uses the text of the first message in the PR, which would be inappropriate since it contains the Preview and Diff links as well as our checklist, etc. It doesn't look like we've landed any PRs since this change happened. Merge Queue seems to be useful for repos with a very high commit rate, to avoid conflicts with manually merging. But this repo gets ~1 commit / month so it doesn't feel necessary :) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/1075 You are receiving this because you are subscribed to this thread. Message ID: <w3c/manifest/issues/1075@github.com>
Received on Monday, 24 April 2023 04:24:33 UTC