Differences

This shows you the differences between two versions of the page.

--- fxdemo:05-part:17-git-and-review-workflow:17-3-commit-conventions:start [2026/08/12 15:43] – created owen
+++ fxdemo:05-part:17-git-and-review-workflow:17-3-commit-conventions:start [2026/08/12 15:44] (current) – owen
@@ Line 9: / Line 9: @@
 A commit message should identify the kind of change and its subject. The team may use a simple convention such as:
-  * docs: update tool baseline checklist rules
+  * ''docs: update tool baseline checklist rules''
-  * script: add prerequisite validation
+  * ''script: add prerequisite validation''
-  * idl: add node status type
+  * ''idl: add node status type''
-  * node: add validation node lifecycle handling
+  * ''node: add validation node lifecycle handling''
-  * config: add baseline DDS QoS profile
+  * ''config: add baseline DDS QoS profile''
-  * test: add control-plane status validation
+  * ''test: add control-plane status validation''
-  * container: add observer container definition
+  * ''container: add observer container definition''
 A commit should not mix unrelated changes unless the team intentionally bundles them for a reviewed Baseline update. For example, a change to an IDL file may properly include regenerated type Artifacts and affected tests. A change to spelling in documentation should not also change runtime behavior.
-Developers should not commit local virtual environments, temporary logs, build outputs, local overrides, editor caches, machine-specific files, or unmanaged generated Artifacts. The .gitignore file should support this rule, but developers remain responsible for reviewing staged changes before committing.
+Developers should not commit local virtual environments, temporary logs, build outputs, local overrides, editor caches, machine-specific files, or unmanaged generated Artifacts. The ''.gitignore'' file should support this rule, but developers remain responsible for reviewing staged changes before committing.
 ----