Installs the workflow that publishes accepted milestones, as requested by S01 (the template was supplied in chat).
.gitea/workflows/sync-milestones.yml: on a push to main that changes docs/milestones/** or docs/sqa/reviews/**, runs sync-project.sh --accepted-only --apply; a manual run is a dry run unless dry_run is switched off. Adapted from the template in two ways: the secret is the bare TOKEN_FOR_GITEA (this project no longer uses a JSON secret), and the job declares permissions: contents: read.
framework is bumped from v0.3.1-2 to v0.5.2 (and framework/qc with it): --accepted-only exists from v0.5.0 and the script computes the project root from its own location, so the mounted framework must have it. The flat qc/ layout is unchanged in v0.5.2, so no document link breaks; 305 tests pass.
Home (README, Danish and Malay pages): the workflow table lists it and a PlantUML diagram shows its flow (a test requires every workflow to be listed and drawn).
What merging this does: installing the file is the standing authorization to publish. After the merge, every later push to main that changes the milestones or their reviews creates or updates milestones and issues for the accepted ones; Proposed milestones are skipped (MIL-007 is Proposed on main right now, so it is skipped until its latest row is Accepted).
Open points before it can work:
TOKEN_FOR_GITEA must be allowed to write issues and milestones and to read the framework repository TirSystem/SQA-QC-Framework (submodule over HTTPS). I cannot read the scope of an organization secret; the first manual dry run will show whether the checkout works, and a real run whether writes are allowed.
Run it once by hand with dry_run on after the merge.
Wiki pages changed: Home (en, da, ms).
No issue closed: requested by the user.
Installs the workflow that publishes accepted milestones, as requested by S01 (the template was supplied in chat).
- `.gitea/workflows/sync-milestones.yml`: on a push to `main` that changes `docs/milestones/**` or `docs/sqa/reviews/**`, runs `sync-project.sh --accepted-only --apply`; a manual run is a dry run unless `dry_run` is switched off. Adapted from the template in two ways: the secret is the bare `TOKEN_FOR_GITEA` (this project no longer uses a JSON secret), and the job declares `permissions: contents: read`.
- `framework` is bumped from v0.3.1-2 to v0.5.2 (and `framework/qc` with it): `--accepted-only` exists from v0.5.0 and the script computes the project root from its own location, so the mounted framework must have it. The flat `qc/` layout is unchanged in v0.5.2, so no document link breaks; 305 tests pass.
- Home (README, Danish and Malay pages): the workflow table lists it and a PlantUML diagram shows its flow (a test requires every workflow to be listed and drawn).
**What merging this does:** installing the file is the standing authorization to publish. After the merge, every later push to `main` that changes the milestones or their reviews creates or updates milestones and issues for the accepted ones; Proposed milestones are skipped (MIL-007 is Proposed on `main` right now, so it is skipped until its latest row is Accepted).
**Open points before it can work:**
- `TOKEN_FOR_GITEA` must be allowed to write issues and milestones and to read the framework repository `TirSystem/SQA-QC-Framework` (submodule over HTTPS). I cannot read the scope of an organization secret; the first manual dry run will show whether the checkout works, and a real run whether writes are allowed.
- Run it once by hand with `dry_run` on after the merge.
Wiki pages changed: Home (en, da, ms).
No issue closed: requested by the user.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Installs the workflow that publishes accepted milestones, as requested by S01 (the template was supplied in chat).
.gitea/workflows/sync-milestones.yml: on a push tomainthat changesdocs/milestones/**ordocs/sqa/reviews/**, runssync-project.sh --accepted-only --apply; a manual run is a dry run unlessdry_runis switched off. Adapted from the template in two ways: the secret is the bareTOKEN_FOR_GITEA(this project no longer uses a JSON secret), and the job declarespermissions: contents: read.frameworkis bumped from v0.3.1-2 to v0.5.2 (andframework/qcwith it):--accepted-onlyexists from v0.5.0 and the script computes the project root from its own location, so the mounted framework must have it. The flatqc/layout is unchanged in v0.5.2, so no document link breaks; 305 tests pass.What merging this does: installing the file is the standing authorization to publish. After the merge, every later push to
mainthat changes the milestones or their reviews creates or updates milestones and issues for the accepted ones; Proposed milestones are skipped (MIL-007 is Proposed onmainright now, so it is skipped until its latest row is Accepted).Open points before it can work:
TOKEN_FOR_GITEAmust be allowed to write issues and milestones and to read the framework repositoryTirSystem/SQA-QC-Framework(submodule over HTTPS). I cannot read the scope of an organization secret; the first manual dry run will show whether the checkout works, and a real run whether writes are allowed.dry_runon after the merge.Wiki pages changed: Home (en, da, ms).
No issue closed: requested by the user.