How to Get Your Zephyr Patches Merged
summary
Concrete checklist for getting Zephyr patches merged: show code for the Zephyr® Project, use git and GitHub forks, format commits as one-change units with clear short log lines and a detailed body, include Signed-off-by: and follow the subsystem: summary convention, avoid fix-up commits by squashing with git rebase -i, keep a linear branch, respond to CI failures and review comments, update via rebase not new PRs, use west for third‑party modules, seek attention on Discord or designated meetings and escalate to the TSC if needed.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:17Prerequisites
- 7:15Commit vs Pull Request
- 12:35Commit Messages
- 16:42Commit Log Example
- 24:40Review Comments
- 27:52Review Time
- 31:52Resolving Disputes
related talks
40mContributing to Zephyr vs (Linux and U-boot)
37mGetting Your Patches in Mainline Linux: What Not To Do (& a Few Things You Could Try
40mWorking with the Community: A Timeline for Adding Support for a New Board in Zephyr
43mZephyr Project: Results from Applying Open Source and Security Best Practices
48mGraphing Zephyr Development and Project Health and How Visualizing Data Help with Gr...
40m9 Years in the Making, the Story of Zephyr, Starting with Commit Nr. 1
56mMeet the Maintainers BoF
37mManifests: Project Sanity in the Ever-Changing Zephyr World