- publish-wiki-pages.yml: reusable workflow with wiki_dir, prune and tools-ref inputs and the declared secret TOKEN_FOR_GITEA_WIKI - tools/publish_wiki.py: WIKI_PRUNE selects explicit mode without the marker; a missing folder is a configuration error - publish-own-wiki.yml: this repository calls the reusable workflow - wiki/ moves to docs/wiki/; build_wiki.py and its tests follow - the scoped publish-wiki.yml is marked deprecated, not removed - guides, README and the Danish and Bahasa Malaysia wiki pages describe the caller, docs/wiki/ and the new error messages Task: MIL-008#2 Task: MIL-008#4 Task: MIL-008#5 Task: MIL-008#6
2.5 KiB
2.5 KiB
This page is generated from
README.md. Changes made here are overwritten the next time the wiki is published.
English | Dansk | Bahasa Melayu
Capabilities
Rows that say Implemented or Guides written exist today. The rest is planned and tracked in the Project Plan, which also describes each use case.
| Capability | Status |
|---|---|
| Synchronize repository metadata (Gitea to GitHub mirror) | Implemented in .gitea/scoped_workflows/, with offline tests and a validation workflow |
| Configure and validate workflow credentials | Implemented for the sync workflow: preflight checks both tokens before any change (guide) |
| Onboard a repository, manage runners, diagnose failures | Guides written (onboarding, troubleshooting); scoped delivery to the repositories of all four organizations verified (MIL-002) |
Publish a repository wiki from wiki/ (opt-in, delivered to every organization) |
Implemented in .gitea/scoped_workflows/publish-wiki.yml, with offline tests; a pilot in a second repository publishes its wiki (MIL-006); being replaced by the reusable workflow below (ADR-0009) |
Publish a repository wiki from docs/wiki/ through a called workflow |
Implemented as the reusable workflow .gitea/workflows/publish-wiki-pages.yml, with offline tests; this repository's own wiki is in docs/wiki/ and published by it through publish-own-wiki.yml; not yet called from another repository (MIL-008) |
| Shared quality checks (Python and shell) | Implemented as the reusable workflow .gitea/workflows/quality-checks.yml, with offline tests and a trial in a second organization; adopted in RepoFoundry (guide) |
| Shared quality checks (C and C++, C#) | Implemented as the reusable workflows .gitea/workflows/quality-checks-cpp.yml and .gitea/workflows/quality-checks-csharp.yml with exact tool versions and offline tests; not yet used in another repository (MIL-007) (C and C++ guide, C# guide) |
| Versioned release and publishing | Release process, changelog and upgrade guide defined; the release workflow exists and v1.0.0 is released (MIL-004) (guide) |