CI: label manual PR verification runs #68

Merged
alexander merged 5 commits from mcp/pr-labelled-verification into main 2026-09-20 11:01:41 +02:00
Owner

Summary

Manual pull-request.yml runs currently expose three independent identifiers that are easy to conflate:

  • the Forgejo PR number (for example #68);
  • the repository Actions run number (for example #166);
  • Forgejo's internal/backend run ID (for example 168).

Those counters remain independent by design. This change does not attempt to align, skip, or manipulate Forgejo run/database counters.

The manual PR verification form now requires a pr_number input and declares the preferred run title:

PR #<number> — <branch>

using PR #${{ inputs.pr_number }} — ${{ forgejo.ref_name }}.

Forgejo 16.0.4 UI limitation and fallback

The live Forgejo 16.0.4 instance accepts/parses top-level run-name, but does not currently use it as the Actions run title: both the existing Build APK workflow and this PR's self-dispatch are recorded under their static workflow names.

To make the PR identity visible on the current instance, every existing PR-verification check/job is therefore prefixed with PR #<number>. The top-level run-name remains in place so the preferred PR #<number> — <branch> title is used automatically if/when the Forgejo server surfaces it.

No jobs were added or removed.

PR/ref validation

The workflow performs a small read-only validation before the existing policy gate:

  • the supplied PR number must be a positive integer;
  • Forgejo's public refs/pull/<number>/head is resolved with git ls-remote;
  • that PR head SHA must exactly match the checked-out branch/ref HEAD.

This uses no repository write permission, no new secret, and no automatic Forgejo token. A mismatched PR number/branch fails before Android verification.

Preserved behavior

The existing manual-dispatch gate and verification semantics remain intact, including current-main ancestry, classpath detection, force_rerun, concurrency, secret stripping, immutable action pins, Gradle wrapper validation, gitleaks, Room schema immutability, verifyDebug, Gradle cache policy, artifact uploads, timeouts, and runner/container images.

Verification

  • Refreshed main at f5de0bd87017d3c660d30072c3b5d37e5d340b32.
  • Confirmed Forgejo server 16.0.4+gitea-1.22.0 accepts the documented run-name, workflow_dispatch string input, inputs, forgejo.ref_name, and dynamic job-name expression surfaces.
  • Confirmed Forgejo recognizes the edited .forgejo/workflows/pull-request.yml on this branch.
  • Diff review confirms the PR changes only .forgejo/workflows/pull-request.yml and the matching operator paragraph in docs/release.md.
  • Confirmed action pins, timeouts, runner/container image, concurrency behavior, current-main gate, force_rerun path, token stripping, and verifyDebug command are unchanged.
  • Confirmed no new permissions: block and no new secrets were introduced.
  • Self-dispatch for PR #68 accepted pr_number=68 and force_rerun=false.
  • Forgejo parsed that run into five jobs named PR #68 · …, proving the current-instance check-name fallback works before execution.
  • A Forgejo ref probe of refs/pull/68/head resolves the current PR head 7dfd1adc5ae26d54b5e8119bd22a1281c96189ea.
  • The self-dispatch ran as repository Actions run #166 / Forgejo internal run ID 168 on Runner v13.1.0.
  • The live runner logged Validated PR #68 -> mcp/pr-labelled-verification @ 7dfd1adc., then preserved the existing workflow-file classification path with verification_mode=rerun.
  • The policy, wrapper validation, gitleaks, and committed Room-schema jobs succeeded under their PR #68 · … names.
  • Aggregate verifyDebug completed successfully: BUILD SUCCESSFUL in 8m 12s, 1,184 actionable tasks executed.
  • Existing artifact uploads completed, including the debug APK; the whole self-dispatch finished with status success at 2026-09-20 10:55:30 +02:00.
## Summary Manual `pull-request.yml` runs currently expose three independent identifiers that are easy to conflate: - the Forgejo PR number (for example `#68`); - the repository Actions run number (for example `#166`); - Forgejo's internal/backend run ID (for example `168`). Those counters remain independent by design. This change does not attempt to align, skip, or manipulate Forgejo run/database counters. The manual PR verification form now requires a `pr_number` input and declares the preferred run title: `PR #<number> — <branch>` using `PR #${{ inputs.pr_number }} — ${{ forgejo.ref_name }}`. ## Forgejo 16.0.4 UI limitation and fallback The live Forgejo 16.0.4 instance accepts/parses top-level `run-name`, but does not currently use it as the Actions run title: both the existing Build APK workflow and this PR's self-dispatch are recorded under their static workflow names. To make the PR identity visible on the current instance, every existing PR-verification check/job is therefore prefixed with `PR #<number>`. The top-level `run-name` remains in place so the preferred `PR #<number> — <branch>` title is used automatically if/when the Forgejo server surfaces it. No jobs were added or removed. ## PR/ref validation The workflow performs a small read-only validation before the existing policy gate: - the supplied PR number must be a positive integer; - Forgejo's public `refs/pull/<number>/head` is resolved with `git ls-remote`; - that PR head SHA must exactly match the checked-out branch/ref HEAD. This uses no repository write permission, no new secret, and no automatic Forgejo token. A mismatched PR number/branch fails before Android verification. ## Preserved behavior The existing manual-dispatch gate and verification semantics remain intact, including current-main ancestry, classpath detection, `force_rerun`, concurrency, secret stripping, immutable action pins, Gradle wrapper validation, gitleaks, Room schema immutability, `verifyDebug`, Gradle cache policy, artifact uploads, timeouts, and runner/container images. ## Verification - Refreshed `main` at `f5de0bd87017d3c660d30072c3b5d37e5d340b32`. - Confirmed Forgejo server `16.0.4+gitea-1.22.0` accepts the documented `run-name`, `workflow_dispatch` string input, `inputs`, `forgejo.ref_name`, and dynamic job-name expression surfaces. - Confirmed Forgejo recognizes the edited `.forgejo/workflows/pull-request.yml` on this branch. - Diff review confirms the PR changes only `.forgejo/workflows/pull-request.yml` and the matching operator paragraph in `docs/release.md`. - Confirmed action pins, timeouts, runner/container image, concurrency behavior, current-main gate, `force_rerun` path, token stripping, and `verifyDebug` command are unchanged. - Confirmed no new `permissions:` block and no new secrets were introduced. - Self-dispatch for PR #68 accepted `pr_number=68` and `force_rerun=false`. - Forgejo parsed that run into five jobs named `PR #68 · …`, proving the current-instance check-name fallback works before execution. - A Forgejo ref probe of `refs/pull/68/head` resolves the current PR head `7dfd1adc5ae26d54b5e8119bd22a1281c96189ea`. - The self-dispatch ran as repository Actions run `#166` / Forgejo internal run ID `168` on Runner `v13.1.0`. - The live runner logged `Validated PR #68 -> mcp/pr-labelled-verification @ 7dfd1adc.`, then preserved the existing workflow-file classification path with `verification_mode=rerun`. - The policy, wrapper validation, gitleaks, and committed Room-schema jobs succeeded under their `PR #68 · …` names. - Aggregate `verifyDebug` completed successfully: `BUILD SUCCESSFUL in 8m 12s`, 1,184 actionable tasks executed. - Existing artifact uploads completed, including the debug APK; the whole self-dispatch finished with status `success` at 2026-09-20 10:55:30 +02:00.
alexander force-pushed mcp/pr-labelled-verification from 7dfd1adc5a to fd9400cb1b 2026-09-20 11:01:14 +02:00 Compare
alexander deleted branch mcp/pr-labelled-verification 2026-09-20 11:01:41 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
alexander/Audiobookshelf-Manager-Claude!68
No description provided.