kevingurney commented on PR #36549: URL: https://github.com/apache/arrow/pull/36549#issuecomment-1626403004
I did a quick search online about ways to disable the green merge button in the UI to prevent others from accidentally making the same mistake in the future. Unfortunately, it seems like there isn't an easy way to do this. There do appear to be a few "workarounds" suggested online (e.g. [this article](https://www.jessesquires.com/blog/2021/08/24/useful-label-based-github-actions-workflows/#do-not-merge)), such as creating a CI workflow that will unconditionally fail if a certain label is present on the PR. However, this has the major downside that the default PR CI status would always include a failing workflow, which does not feel ideal. Perhaps, a more straightforward solution would be to create some kind of "Getting Started as a Committer" guide (or something to that effect), with https://github.com/apache/arrow/blob/41e08795864b96f8fbbc9c42975d82e3bb0bb6d1/dev/README.md#how-to-merge-a-pull-request included as "required reading". If that sounds helpful, I could follow up with a PR for that and work with other community members to ensure that it contains any other important references and is included in any materials that are shared with new committers. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
