Skip to content

Conversation

@JarmouniA
Copy link
Contributor

@JarmouniA JarmouniA commented Oct 28, 2025

Clarify the process for managing and reviewing pull requests with serial dependencies. This helps contributors understand how to structure, propagate changes, and validate dependent PRs effectively.

Originated from #90216 (comment)

Doc preview https://builds.zephyrproject.io/zephyr/pr/98391/docs/contribute/contributor_expectations.html#contributor-expectations

@JarmouniA JarmouniA marked this pull request as ready for review October 28, 2025 10:51
@JarmouniA JarmouniA force-pushed the doc_contributor_multiple_PRs branch from 61d4777 to 9041daa Compare October 28, 2025 11:00

- Propagate Changes

Any updates to PR A must be manually propagated to PR B, and then from PR B to PR C.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mention that propagation must happen after the PR is merged.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean PR B is rebased on main after A is merged?

Clarify the process for managing and reviewing pull requests with serial
dependencies. This helps contributors understand how to structure,
propagate changes, and validate dependent PRs effectively.

Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
@JarmouniA JarmouniA force-pushed the doc_contributor_multiple_PRs branch from 9041daa to 68e157c Compare October 28, 2025 12:26
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants