Hi everyone, I would like to propose enabling GitHub’s auto-merge feature for the core Cloudberry repository.
Auto-merge could help us reduce the manual work involved in merging pull requests. Once a PR has received the required approvals and all required CI checks have passed, GitHub can merge it automatically. More information about this feature is available in the GitHub documentation: https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/automatically-merging-a-pull-request One point we should keep in mind is commit history. Auto-merge may not be appropriate when a PR contains multiple commits that should first be squashed, reordered, or otherwise cleaned up. In those cases, the PR author or maintainer should clean up the commit history before enabling auto-merge, or merge the PR manually after the necessary changes are made. My initial proposal is: - Enable auto-merge for the repository. - Use it only after the PR has received the required reviews and passed CI. - Ensure that the commit history is in an acceptable state before enabling auto-merge. - Handle PRs requiring squash or other history cleanup manually. Please share your thoughts and any concerns before we proceed. Best, Dianjin Wang --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
