generated from erix/meta
[FEATURE] Add useful CI job summaries #7
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-partition#7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Problem and motivation
Reviewing this repository's CI requires reading long logs to find outcomes and evidence. Native job summaries should make that information easy to find.
Proposed behavior and scope
Publish a concise Markdown summary for each executed CI job in
lib-partition, usingFORGEJO_STEP_SUMMARYand Integration's shared reporting contract. Include the source commit, provider snapshot when applicable, check outcomes, useful counts/timings and links to logs or artifacts.Apply this to
.github/workflows/ci.yml.Authority, security and reliability
Write only to the runner-provided summary file and approved existing outputs. Escape dynamic Markdown, keep secrets and private paths out, and preserve original exit statuses and all validation, timeout and authority checks. Missing evidence must stay explicit; reporting cannot turn a failure or skipped check into a pass.
Acceptance criteria
Alternatives and tradeoffs
Keep full logs and artifacts for detailed investigation. Reuse Integration's reporting contract rather than maintaining a separate formatter or copied test suite here.
Tracking and rollout
Alpha 1 work, dependent on the shared CI job-summary implementation. See the shared rollout for the contract and rollout checklist.