Hi everyone,

As we currently have quite a few PRs waiting to be merged, I'd like to
share a small suggestion to help improve our PR merging efficiency and
make better use of CI resources.

As our PR merging process requires each PR to be rebased against the
latest main branch and pass CI tests, the timing of rebasing and
testing matters.

For example, if another approved PR is already undergoing CI testing
and is likely to be merged soon, starting the rebase and CI process
for your own approved PR at the same time may result in unnecessary
work. Once the ongoing PR is merged, the main branch will have moved
forward, potentially requiring your approved PR to be rebased again
against the updated main branch and its CI tests to be rerun.

To avoid such situations, before rebasing a PR for merging, please
check whether another approved PR is already undergoing final CI
testing and is expected to be merged soon. If so, consider waiting
until that PR has been merged before rebasing and testing yours.

You can see all the approved PRs and check their status here:
https://github.com/apache/cloudberry/pulls?q=is%3Apr+state%3Aopen+review%3Aapproved

This simple coordination can help us:
* Avoid unnecessary rebases and repeated CI runs.
* Reduce CI resource consumption and contention.
* Make the overall PR merging process more efficient.

Thanks for your understanding and cooperation!


Best,
Dianjin Wang

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to