CI: label manual PR verification runs #68
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/pr-labelled-verification"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Manual
pull-request.ymlruns currently expose three independent identifiers that are easy to conflate:#68);#166);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_numberinput 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-levelrun-nameremains in place so the preferredPR #<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:
refs/pull/<number>/headis resolved withgit ls-remote;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
mainatf5de0bd87017d3c660d30072c3b5d37e5d340b32.16.0.4+gitea-1.22.0accepts the documentedrun-name,workflow_dispatchstring input,inputs,forgejo.ref_name, and dynamic job-name expression surfaces..forgejo/workflows/pull-request.ymlon this branch..forgejo/workflows/pull-request.ymland the matching operator paragraph indocs/release.md.force_rerunpath, token stripping, andverifyDebugcommand are unchanged.permissions:block and no new secrets were introduced.pr_number=68andforce_rerun=false.PR #68 · …, proving the current-instance check-name fallback works before execution.refs/pull/68/headresolves the current PR head7dfd1adc5ae26d54b5e8119bd22a1281c96189ea.#166/ Forgejo internal run ID168on Runnerv13.1.0.Validated PR #68 -> mcp/pr-labelled-verification @ 7dfd1adc., then preserved the existing workflow-file classification path withverification_mode=rerun.PR #68 · …names.verifyDebugcompleted successfully:BUILD SUCCESSFUL in 8m 12s, 1,184 actionable tasks executed.successat 2026-09-20 10:55:30 +02:00.7dfd1adc5atofd9400cb1b