michaelsembwever commented on code in PR #311: URL: https://github.com/apache/cassandra-website/pull/311#discussion_r2910033783
########## site-content/source/modules/ROOT/pages/development/how_to_commit.adoc: ########## @@ -4,10 +4,37 @@ Commits applicable to multiple versions are atomically pushed forward merges. -The fix lands on the oldest release branch and is then forward-merges it into each newer branch using an ours merge to record branch lineage and amends that merge commit to include the branch-appropriate patch. +Fix land on the oldest release branch, and are then forward-merged onto each newer branch using an ours merge strategy to record branch lineage. Each forward-merge commit contains the branch-appropriate patch. This keeps a clean, traceable history and a single logical unit of work per ticket per branch, while preventing unintended diffs from being pulled forward automatically. +== Introduction for New Committers + +To be an effective committer, you should be familiar with the following background details. While this is not a git tutorial, it outlines the expected workflow: + +* **Using CLI vs GitHub web UI:** We recommend using the Git CLI rather than the GitHub web UI. Review Comment: ```suggestion To be an effective committer, you should be familiar with the following git command lines. The following outlines the simple trunk-only patch workflow. See next section for multi-branch contributions * **Using CLI vs GitHub web UI:** We recommend using the Git CLI rather than the GitHub web UI. ``` -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
