Skip to content

FLX-ENG-RFC-002-US-1.7 - CodePulse Rules and Exclusions

Field Value
Parent RFC FLX-ENG-RFC-002
GitHub Issue #15 - US-1.7
Owner Arun Singh
Priority P1
Status Blocked until US-1.6 and release-sync answers are complete
Target window Day 1 or Day 2

Goal

Configure CodePulse deployment and incident rules so DORA metrics reflect real delivery behavior instead of docs-only changes, bots, draft PRs, or sync noise.

Rule Set

Signal Rule
Deployment PR merge to confirmed production branch, usually main
Incident Revert PR, hotfix branch, or explicitly linked incident issue
Excluded PR Bot-authored, docs-only, draft, generated, sync-only
Timezone Asia/Kolkata unless Flexli leadership chooses otherwise

Approaches Considered

Approach Pros Cons
PR merge to main as deployment Simple, automatable Wrong if production deploy is manual/tag-based
Release tag as deployment More accurate for tagged releases Fails if tags are not consistently used
Manual deployment marker Accurate More process burden

Verdict

Use PR merge to the confirmed production branch unless the sync meeting proves releases are tag/manual driven. Document the decision in the scan report.

Implementation Steps

  1. Confirm production branch from US-1.4.
  2. Configure deployment rule.
  3. Configure incident rule for revert PRs.
  4. Configure excluded PR filters:
  5. docs/** only
  6. bot authors
  7. draft PRs
  8. sync-agent-only PRs
  9. generated-only changes
  10. Validate against two historical PRs.
  11. Document final rules in docs/runbooks/ or the Week 1 scan report.

Test Cases

  • One real application PR counts as deployment.
  • One docs-only PR is excluded.
  • One bot/sync PR is excluded.
  • One revert/hotfix event is classified as incident or flagged for manual review.

Gating

  • Do not finalize rules before release sync evidence.
  • Do not include all PRs by default if sync/doc PRs dominate the repo.
  • File a gap issue if historical PRs are insufficient to validate rules.

Definition of Completion

  • Rules active in CodePulse.
  • Two historical PRs verified.
  • Exclusion policy documented.
  • US-2.1 passive collection can start.

Reviewer Reply Template

Thanks, I tuned the CodePulse rules against historical PRs so docs and sync noise do not distort DORA metrics.