docs: absorb DORA docs repo into forgejo-mcp/docs/ #29
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
test:label-a
test:label-b
test:set-label
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/forgejo-mcp#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Discovered during DORA board migration session 2026-06-13.
Repo
ldraney/forgejo-mcp
User Story
As a platform operator I want DORA documentation next to the Forgejo tooling repo so that docs and code live together and I don't maintain a docs-only repo.
Context
The ldraney/DORA repo is docs-only — 4 markdown files (architecture, metrics reference, tiering, dashboard specs) with no code. Since forgejo-mcp wraps the Forgejo API and git is the heart of DORA, these docs belong here. Eliminates repo sprawl.
File Targets
Files to create:
docs/architecture.md— data flow from Forgejo/Woodpecker through Prometheus to Grafanadocs/metrics.md— every Prometheus metric the exporter emitsdocs/tiering.md— repo tier system for Grafana filteringdocs/dashboard.md— current panels, PromQL queries, planned improvementsFiles to modify:
README.md— add DORA Docs table linking to local docsFeature Flag
None needed.
Acceptance Criteria
Test Expectations
Constraints
Checklist
Related