Add automation governance and release strategy doc

[ashleyshaw]

Introduces AUTOMATION_GOVERNANCE.md outlining standards for changelog enforcement, release automation, labelling, branching, and project sync across all LightSpeed repositories. Provides detailed policies, recommended workflows, and references for maintainers and contributors.

Summary by CodeRabbit

• Documentation
  • Introduced a centralised automation governance guide outlining org-wide policies and workflows for changelogs, release automation, labelling, project syncing, and branching discipline.
  • Covers principles (automation-first, standard workflows, semantic versioning), required PR/CI checks, release steps (validation, tagging, publishing), label rules and colour consistency, changelog format and version-bump triggers, example tool configurations, project field alignment, secrets/permissions guidance, rollout plan, and maintainer usage notes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Adds a new org-wide documentation file, AUTOMATION_GOVERNANCE.md, defining policies and workflows for changelogs, releases, labelling, project syncing, branching, CI checks, secrets/permissions, rollout, and usage guidance across LightSpeed repositories.

Changes

Cohort / File(s)	Summary
Documentation: Governance AUTOMATION_GOVERNANCE.md	New governance document outlining automation-first principles, required workflows (changelog enforcement, release automation, labelling, project updates), branching conventions, CI checks, changelog format, versioning triggers, tool configs, secrets/permissions, rollout, and references.

Sequence Diagram(s)

sequenceDiagram
autonumber
actor Dev as Developer
participant Repo as Repo (PR/CI)
participant Auto as Automation Bot
participant GH as GitHub Releases
participant Project as Project Board
rect rgba(230,245,255,0.5)
note over Dev,Repo: PR Creation & Changelog Enforcement
Dev->>Repo: Open PR with template
Repo->>Repo: CI checks changelog Unreleased entry
Repo-->>Dev: Pass/Fail status
end
rect rgba(235,255,235,0.5)
note over Auto: Labelling & Sync
Repo->>Auto: PR event (open/sync/merge)
Auto->>Auto: Apply labels (type/branch)
Auto->>Project: Update fields/status
end
rect rgba(255,245,230,0.5)
note over Dev,Auto: Release Automation
Dev->>Auto: Trigger release (label/version)
Auto->>Repo: Validate changelog format
Auto->>Auto: Determine version (semver, BREAKING CHANGE)
Auto->>Repo: Move Unreleased -> dated section
Auto->>GH: Create tag and GitHub Release
Auto->>GH: Attach artefacts (optional)
Auto-->>Repo: Status output
end

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I thump my paws in tidy cheer,
New rules align our burrows here.
Labels hop, releases flow,
Changelogs sprout in ordered rows.
With whiskered wit and CI light,
We ship at dawn, tails tucked tight. 🐇✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch develop

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 675b97c and 1696ceb.

📒 Files selected for processing (1)

• AUTOMATION_GOVERNANCE.md (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}