Commit b4ea1c20b8
Verified · cmc
docs/roadmap.org +4 −3
| @@ -24,11 +24,12 @@ What it is today: an excellent forge for its author and for CLI-native | ||
| 24 | 24 | individuals. What it is not yet: a forge a GitHub-habituated *team* |
| 25 | 25 | would stay on, or a project outsiders can easily run themselves. |
| 26 | 26 | |
| 27 | * Phase 1 — collaboration credibility | |
| 27 | * Phase 1 — collaboration credibility [COMPLETE 2026-08-24] | |
| 28 | 28 | |
| 29 | 29 | Goal: a second contributor works here for a week and misses nothing they |
| 30 | would act on. These compound: statuses gate merges, notifications close | |
| 31 | the feedback loop, inline comments make review real. | |
| 30 | would act on. All five shipped: deploy keys, commit statuses with | |
| 31 | require-checks gating, email notifications, inline review threads, and | |
| 32 | required approvals with CODEOWNERS and require-resolved. | |
| 32 | 33 | |
| 33 | 34 | - [[https://gitbay.org/krz/gitbay/issues/22][#22]] deploy keys — smallest item, unblocks CI checkout; the scope |
| 34 | 35 | already exists in the policy layer |