Define development workflow (branching, commits, reviews) #2

New Issue

2026-07-22T16:15:40Z

Ninosaurier commented

2026-07-22 16:15:40 +00:00

Context

A consistent workflow for how changes get proposed, reviewed, and merged is what allows a project to scale beyond a single contributor without losing quality or introducing undocumented architectural drift.

What was done

Defined the expected contribution flow: branch from main, run local checks (lint, unit tests, component tests), open a Pull Request
Established that PRs are reviewed on three levels: automated checks, architectural compliance, and general project quality — and that a PR can be rejected even with green checks if it conflicts with documented architecture
Defined the changeset requirement for any user-facing change, to keep versioning and changelog generation consistent
Documented the expectation that any code change invalidating an ADR/ADM statement must update that document in the same PR, including a Change Log entry

Outcome

Full contribution workflow documented in CONTRIBUTING.md
Local commands for lint/test documented and verified to work (pnpm lint, pnpm test:unit, pnpm test:component)

## Context A consistent workflow for how changes get proposed, reviewed, and merged is what allows a project to scale beyond a single contributor without losing quality or introducing undocumented architectural drift. ## What was done - Defined the expected contribution flow: branch from `main`, run local checks (lint, unit tests, component tests), open a Pull Request - Established that PRs are reviewed on three levels: automated checks, architectural compliance, and general project quality — and that a PR can be rejected even with green checks if it conflicts with documented architecture - Defined the changeset requirement for any user-facing change, to keep versioning and changelog generation consistent - Documented the expectation that any code change invalidating an ADR/ADM statement must update that document in the same PR, including a Change Log entry ## Outcome - Full contribution workflow documented in **CONTRIBUTING.md** - Local commands for lint/test documented and verified to work (`pnpm lint`, `pnpm test:unit`, `pnpm test:component`) ## Related - `CONTRIBUTING.md`

Ninosaurier added this to the v0.1.0 - Phase 1: Groundwork milestone 2026-07-22 16:15:40 +00:00

Ninosaurier self-assigned this 2026-07-22 16:15:40 +00:00

Ninosaurier added the Kind/Enhancement Priority/High labels 2026-07-22 19:10:28 +00:00

Ninosaurier referenced a pull request that will close this issue

2026-08-04 12:09:52 +00:00

ci(component-tests): add containerized component test workflow #14

Ninosaurier closed this issue

2026-08-04 12:34:05 +00:00

Sign in to join this conversation.