How to Configure Commit Enforcement

Configure the enforcement level to match your team's current compliance maturity without disabling it entirely, which is not possible.

Goal: Configure the enforcement level that best matches your team's current compliance maturity. Note: DISABLED is not an available level. This was evaluated. It was rejected. The rejection is documented.

Enforcement Levels

Select the level that best describes the gap between your team's current practice and the standard you are working toward. WRAAS evaluated all levels, including a level below ADVISORY. That level is not available.

Level	Code	Behaviour
Strict	`STRICT`	All violations block. No exceptions. Scopes required. WRAAS is satisfied.
Standard	`STANDARD`	Default. Blocking violations block. Non-blocking are flagged and added to a report that will be reviewed.
Lenient	`LENIENT`	Only blocking violations block. Non-blocking generate a report. The report does not disappear on its own.
Advisory	`ADVISORY`	Nothing blocks. Everything is noted. Notes accumulate. WRAAS waits.
Disabled	—	Not available. This option was evaluated and rejected. See DME-0088.

Configuration

YAML — wraas.yml

# wraas.yml
commit:
  enforcement: STANDARD
  scope_required: true
  breaking_change_footer: true
  imperative_mood: warn    # 'block' or 'warn'

🔴

Important

Enforcement level DISABLED was evaluated during the design phase. The rejection is documented as DME-0088: "enforcement without effect is noise, and noise is worse than silence, and silence is not the goal." The option is not available.