From 21ee56afe815816eb71e2ba7601fbc84a889f936 Mon Sep 17 00:00:00 2001 From: Albrecht Degering Date: Tue, 7 Jul 2026 21:42:19 +0200 Subject: [PATCH] Sync wiki from project files --- Repo-docs-GITEA-ISSUES.md | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/Repo-docs-GITEA-ISSUES.md b/Repo-docs-GITEA-ISSUES.md index d1d7bd7..7f2b1dc 100644 --- a/Repo-docs-GITEA-ISSUES.md +++ b/Repo-docs-GITEA-ISSUES.md @@ -1,4 +1,4 @@ - + > Mirrored from `/mnt/DATA/git/govoplan-core/docs/GITEA_ISSUES.md`. > Origin: `repository`. @@ -40,7 +40,15 @@ For a shared credentials file outside the target repository, pass `--env-file`: ./scripts/gitea-sync-labels.py --env-file /path/to/private/gitea.env --apply ``` -Create a Gitea token with issue read/write access and label-management permission for the repository. On scoped-token instances, this usually means issue read/write and, if label writes are rejected, repository write permission too. +Create a Gitea token with issue read/write access and label-management +permission for the repository. On scoped-token instances, this usually means +issue read/write and, if label writes are rejected, repository write permission +too. + +For GovOPlaN repositories, prefer organization labels for the shared taxonomy. +Creating or updating organization labels requires a token with +`write:organization`. Repository label management only needs repository label +permission, but it duplicates the taxonomy into each repository. Preview and apply labels: @@ -50,6 +58,19 @@ cd /mnt/DATA/git/govoplan-core ./scripts/gitea-sync-labels.py --apply ``` +Preview and apply the shared taxonomy as organization labels: + +```bash +cd /mnt/DATA/git/govoplan-core +./scripts/gitea-sync-labels.py --scope organization --env-file /home/zemion/.config/gitea/gitea.env +./scripts/gitea-sync-labels.py --scope organization --env-file /home/zemion/.config/gitea/gitea.env --apply +``` + +The import helpers resolve repository labels and organization labels. Repository +labels win when a repository defines the same name locally, but a repository does +not need a local copy of every shared `type/*`, `status/*`, `priority/*`, +`module/*`, `area/*`, `source/*`, or `codex/*` label. + After the `.gitea` files are pushed to the default branch, Gitea will show the issue template chooser. Blank issues are disabled by `.gitea/ISSUE_TEMPLATE/config.yaml`. ## Multiple Repositories And Workspaces @@ -174,7 +195,10 @@ For a broader project import across all local repositories hosted on `git.add-id ./scripts/gitea-import-all-backlogs.py --env-file /home/zemion/.config/gitea/gitea.env --apply ``` -It scans repository and product-directory files with backlog-like names, creates the shared generic labels where needed, imports missing open work, and deduplicates reruns by hidden fingerprint and normalized title. +It scans repository and product-directory files with backlog-like names, resolves +shared labels from the organization label catalogue where available, creates only +missing fallback repository labels when needed, imports missing open work, and +deduplicates reruns by hidden fingerprint and normalized title. ## Mirroring Project Docs Into Gitea Wikis