Editing Development/GitHub (section)

== Commit messages and PR titles ==

All repositories use '''conventional commits'''. Since PRs are squash-merged, the PR title becomes the commit message. The PR title format is enforced.

=== Format ===

<pre>
<type>(<scope>): <Description starting with uppercase>
</pre>

Scope is optional. Description starts with uppercase, does not end with punctuation.

=== Types ===

{| class="wikitable"
! Type !! When to use
|-
| <code>feat</code> || New feature or capability
|-
| <code>fix</code> || Bug fix
|-
| <code>refactor</code> || Code change that neither fixes a bug nor adds a feature
|-
| <code>perf</code> || Performance improvement
|-
| <code>docs</code> || Documentation only
|-
| <code>test</code> || Adding or updating tests
|-
| <code>ci</code> || CI/CD configuration
|-
| <code>chore</code> || Maintenance (dependencies, tooling, config)
|-
| <code>build</code> || Build system or packaging changes
|}

=== Scopes (per repo) ===

Scopes are short identifiers for the area of the codebase. Each repo defines its own set.

'''duralex:'''

<pre>
feat(corpus): Add source metadata discovery
fix(data): Handle missing content element in LEGI XML
refactor(annotations): Split envelope from type definitions
perf(fts): Optimize FTS query for large result sets
</pre>

'''duralex-fr:'''

<pre>
feat(parser): Add KALI collective agreement parser
fix(refs): Correct L/R/D prefix detection for code du travail
</pre>

=== Breaking changes ===

Append <code>!</code> after the scope for breaking changes:

<pre>
refactor(data)!: Rename LegislationArticle fields to match URI scheme
</pre>

The PR body must include a <code>== Breaking changes ==</code> section explaining what breaks and how to migrate.