Improve CI PR verification diagnostics and titles #83
Loading…
Reference in a new issue
No description provided.
Delete branch "mcp/ci-pr-workflow-title"
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?
Follow-up to #82. This PR now owns the PR-verification workflow cleanup rather than creating a competing workflow PR.
Visible naming
CI · PR verification;CI · PR #<number> — <ref>;CI · PR #<number> · ....Collect → summarize → fail-at-the-end verification
./gradlew verifyDebug --continueinvocation;PR feedback
verifyDebugchecks the exact SHA validated by preflight;BookWave / PR verificationremains green on full success / red on failure;ktlint,tests,compile,Room schemaordependencies.Validation so far
verifyDebuginvocation;scripts/ci/pr-diagnostics.pypasses managed Python compile validation;scripts/ci/pr-diagnostics.pypasses managed Ruff lint validation;Do not merge automatically.
Clarify CI PR workflow titlesto Improve CI PR verification diagnostics and titlesAcceptance run for the improved PR gate
Run CI · PR verification once against this PR:
mcp/ci-pr-workflow-title83Because this PR changes
.forgejo/workflows/*, classification should deliberately select the full--rerun-taskspath.Expected behavior:
./gradlew verifyDebug --continueand captures the full log.verifyDebugfails, Room schema, dependency resolution, diagnostics generation and artifact uploads still run.ci-diagnosticsartifact contains the summary plus full Gradle/dependency logs;quality-reportsnow also includes ktlint and raw test-result XML.BookWave / PR verificationpublishes a green check on full success or a red X with a category-specific description on failure.Static validation already completed: Forgejo workflow parsing PASS, diagnostics Python compile PASS, Ruff lint PASS.
Dynamic CI job naming added
The manual PR number is now optional. A lightweight identity job resolves the selected target before the real checks run.
When a PR number is supplied, Forgejo API metadata is used and the downstream jobs are named like:
CI · PR #83 · Improve CI PR verification diagnostics and titles · PreflightCI · PR #83 · Improve CI PR verification diagnostics and titles · verificationCI · PR #83 · Improve CI PR verification diagnostics and titles · publish checkWhen PR number is omitted, the selected Use workflow from branch becomes the label instead, e.g.
CI · mcp/issue-77-sleep-timer-grace · verification.The resolver also verifies that a supplied PR number actually belongs to the selected branch before any expensive Gradle work starts.
Current HEAD:
8db00e9d3ef4f94b71273598d303da2ca20b3f98.Validation: Forgejo workflow parse PASS; job graph exactly
identity → preflight → verification → publish; exactly oneverifyDebug; diagnostics Python compile PASS; Ruff lint PASS.Note: the top-level Actions list row remains the static workflow name
CI · PR verificationon Forgejo 16.0.4 because this server does not render dynamicrun-name. The dynamic PR title/branch is visible in the actual job names and diagnostics.CI output streamlined + artifact failure addressed
The previous #83 verification failure was not a BookWave quality failure:
verifyDebug: success (BUILD SUCCESSFUL);The job turned red only because
quality-reportsattempted to upload ~997 individual report files and Forgejo's artifact endpoint returned repeated HTTP 500 responses.Current workflow fixes that and reduces successful-run noise:
verifyDebugfails;ci-diagnosticsuploads only on a required-check failure;Visible dynamic job labels include both target and workflow source, e.g.
CI · PR #83 · Improve CI PR verification diagnostics and titles · verification · wf:mcp/ci-pr-workflow-title; runs after merge from main will showwf:main.Current HEAD:
dce704d1db054bb8659f96d60473d4d07f539858.Validation: Forgejo workflow parse PASS; job graph exactly identity → preflight → verification → publish; one verifyDebug invocation; diagnostics Python compile PASS; Ruff lint PASS.
A fresh manual run on the current HEAD is still required for runtime acceptance.