-
Notifications
You must be signed in to change notification settings - Fork 228
Pull Request Merge Steps
-
Create a PR for review.
-
Address all comments and feedback. You will need at least one approval from Helix contributors. In order to become a Helix contributor, one must have made at least 5 commits to Helix.
-
Leave a final comment on the PR stating:
This PR is ready to be merged
-
If you have made multiple commits for one PR, these commits will be squashed into one commit at merge time. If this is the case, you must include one final commit message for the squashed commit in your final comment. This way, the squashed commit will be merged into master cleanly, and the history of all commits for the PR will be kept intact for future reference.
-
Helix PMC/Committers will only merge the PRs with no pending comments and with the final approval message from Steps 3 and 4.
Pull Request Description Template
ZooKeeper API module for Apache Helix
DataAccessor for Assignment Metadata
Concurrency and Parallelism for BucketDataAccessor
WAGED Rebalance Pipeline Redesign
WAGED rebalancer Hard Constraint Scope Expansion
IdealState Dependency Removal Progression Remove requested state in Task Framework