@@ -162,3 +162,44 @@ Detailed PowerShell coding conventions are in `.github/instructions/powershell-c
162162- Do not create new Azure Function trigger folders — use the existing five triggers
163163- Do not call ` Write-Output ` in HTTP functions — return an ` [HttpResponseContext] ` (the outer trigger handles ` Push-OutputBinding ` )
164164- Do not hardcode tenant IDs or secrets — use environment variables and ` Get-GraphToken `
165+
166+ ## Commit messages
167+
168+ Generate all commit messages in ** Conventional Commits** format:
169+
170+ ```
171+ <type>(<optional scope>): <description>
172+
173+ [optional body]
174+
175+ [optional footer(s)]
176+ ```
177+
178+ ** Rules:**
179+
180+ - ** Type** is required and must be one of:
181+ - ` feat ` — a new feature
182+ - ` fix ` — a bug fix
183+ - ` docs ` — documentation only
184+ - ` style ` — formatting, whitespace, no code-behavior change
185+ - ` refactor ` — code change that neither fixes a bug nor adds a feature
186+ - ` perf ` — a performance improvement
187+ - ` test ` — adding or correcting tests
188+ - ` build ` — build system or dependency changes
189+ - ` ci ` — CI/CD configuration changes
190+ - ` chore ` — routine maintenance, no production code change
191+ - ` revert ` — reverts a previous commit
192+ - ** Scope** is optional and given in parentheses after the type (e.g. ` feat(identity): ` ). Use a short, lowercase area name when it adds clarity.
193+ - ** Description** is a short, imperative-mood summary ("add", not "added"/"adds"), lowercase, no trailing period, ideally ≤ 72 characters.
194+ - ** Body** (optional) explains the * what* and * why* , not the * how* . Separate it from the description with one blank line.
195+ - ** Breaking changes** are indicated with a ` ! ` before the colon (e.g. ` feat!: ` ) and/or a ` BREAKING CHANGE: ` footer describing the change.
196+ - Reference issues/PRs in the footer where relevant (e.g. ` Closes #123 ` ).
197+
198+ ** Examples:**
199+
200+ ```
201+ feat(identity): add bulk user offboarding endpoint
202+ fix(graph): handle expired token on retry
203+ docs: update authentication model overview
204+ refactor(standards)!: rename remediation parameter
205+ ```
0 commit comments