Require rainbow README section divider

This commit is contained in:
MrSphay
2026-05-03 02:31:00 +02:00
parent 53527aec47
commit 81e717fbcd
6 changed files with 49 additions and 8 deletions

View File

@@ -13,6 +13,7 @@ PROJECT_NAME: PROJECT_DESCRIPTION
- Do not create a release unless explicitly requested.
- If `GITEA_TOKEN` is available locally, use it only for read-only Gitea API checks such as private repository metadata, package-read visibility, and Actions run status. Never print, commit, or store the token.
- After pushing commits that trigger a Gitea workflow, poll the workflow run until it succeeds. If it fails or is cancelled, inspect the failing job/logs, fix the issue when in scope, push again, and repeat the workflow check loop. Fixing and pushing a workflow failure is not a stopping point.
- When the project uses `blueprint.md` and `blueprint.json` for README generation, keep the rainbow `{{ template:section-line }}` divider between major README sections. Do not replace it with plain `---` unless the target renderer cannot display inline images.
## Commands