Development workflow
GitHub is the source of truth for work; this repository is the source of truth for durable knowledge.
Flow
Epic → scoped issue → branch → PR → review → merge.
- Issues are filed from the templates in each repository and land in the COIPE project (github.com/users/fuisl/projects/22), with fields Status, Priority (P0–P2), Size (XS–XL) and Area.
- Issues include context, requirements, acceptance criteria, design and docs links, and what's out of scope.
- A PR is one understandable change and references its issue. Prefer squash merge.
- Move durable decisions out of chat and into ADRs here.
CI
fuisl/coipe runs one required check named checks (lint, typecheck, test, build, scoped to what changed). fuisl/coipe-docs and fuisl/ceo-of-little-people run the same steps for their single app. Private repositories spend GitHub Pro's monthly Actions minutes; self-hosted runners on the home nodes are the next step if they run out.
Branch protection
Not enabled yet (Open items #7). The vgu-graduation rule set is the model: PR required, one approving review, checks passing, conversations resolved, squash only, admin bypass for emergencies.
Roles
| Area | Owner |
|---|---|
| Web, design, docs | fuisl |
| API, data, infrastructure | to agree with horidang10 |