chore: add commit tooling, lint config, and docs/west scaffolding (partial #1) #2
No reviewers
Labels
No labels
Category
App
Category
Documentation
Category
Firmware
Category
Hardware
Category
Qms
PR_Size
L
PR_Size
M
PR_Size
S
PR_Size
XL
PR_Size
XS
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very Low Priority
Size
Epic
Size
Feature
Size
Task
Status
Blocked
Status
Draft
Status
Needs-review
Team
Board
Team
Dev
Team
Management
Type
Bug
Type
Capa
Type
Improvement
Type
New-feature
Type
Regulatory
Type
Usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
opendutchsolutions.public/hal_awr6843!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/2/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Adds the first slice of baseline repo tooling from issue #1: a commitizen config enforcing OpenDutchSolutions' conventional-commit GitFlow, a
.clang-formatmatching Zephyr's style for the C code that's about to land, a Sphinx docs skeleton, a Zephyr west module descriptor (zephyr/module.yml), and.gitignorecoverage for compiler-generated.asmoutput and MISRA tool artifacts.Why
Change justification per ISO 9001 section 7.5.2: before any driver/feature code lands, the repo needs consistent commit formatting, lint rules, and a docs/west integration point in place — otherwise every subsequent PR reinvents its own conventions ad hoc, which is harder to review and harder to keep MISRA-traceable. This is scaffolding, committed early on purpose so later PRs are built against it from the start.
Related Issue
Relates to #1 — this PR only covers 2 of the issue's 4 acceptance criteria (commitizen config, contribution/docs scaffolding). The CMake toolchain files and the CI runner are being tracked and delivered separately, so this PR does not close #1.
Type of Change
Impact Assessment
Testing
.cz.jsonconforms to commitizen'scz_customizeschema and produces the expected commit template; verified.clang-formatparses and matches Zephyr's coding style conventions. Sphinx docs build itself was not run in this PR.PR Size
Size justification / exemption (if L or XL):
267 lines across 7 files, all config/docs, no source code. Five independently-scoped infra commits (commitizen, clang-format, gitignore, west module descriptor, sphinx skeleton) bundled into one PR since they're all part of issue #1's initial-scaffold criteria and each is separately reviewable via its own commit diff; none is large enough alone to justify its own PR.
Checklist
type(scope): descriptionconvention withRelates to #<issue>footerSummary
.cz.json— commitizen config enforcing OpenDutchSolutions GitFlow commit format.clang-format— Zephyr-style C formatting rulesdocs/conf.py,docs/index.rst,docs/requirements.txt— Sphinx docs skeletonzephyr/module.yml— Zephyr west module descriptor.gitignore— ignore compiler-generated.asmoutput and MISRA tool artifacts/output