Skip to content

fix(pana-score): give every scored package its own commit status - #64

Merged
PiotrRogulski merged 2 commits into
masterfrom
claude/pana-score-action-status-5w4e4q
Aug 7, 2026
Merged

PiotrRogulski merged 2 commits into
masterfrom
claude/pana-score-action-status-5w4e4q

Conversation

@PiotrRogulski

Copy link
Copy Markdown
Member

Summary

  • Running the pana-score action once per package in a single PR reported every package under the same hardcoded pana commit status context, so each run overwrote the previous one. The context is now pana (<package-name>), giving each package its own status entry.
  • Added a package-name output (resolved from the package's pubspec.yaml, falling back to its directory name).
  • Package-name resolution now happens first thing in the score step, shielded from set -e, with an unknown last resort — a crash later in the step (or the step being skipped entirely after an earlier failure) no longer leaves the status context to fall back to the bare, collision-prone pana. The status-reporting step also resolves the name independently as a further fallback.
  • Dropped the now-redundant package name from the score output/description text and step-summary header, since the commit status context and description already carry it separately.

Test plan

  • Run a workflow that invokes this action for multiple packages in one PR and confirm each package gets its own pana (<package-name>) commit status instead of overwriting a shared one.
  • Confirm the step summary and score/state/package-name outputs still render correctly for both successful and failing pana runs.

Generated by Claude Code

claude added 2 commits August 3, 2026 12:38
Package-name resolution ran partway through the score step, guarded by
set -e, so a crash before that point (or the whole step being skipped
after an earlier failure) left package-name unset. The status step
then fell back to the bare "pana" context, which every such failure
collided on again.

Resolve the name first thing in the score step, shielded from set -e,
with an "unknown" last resort. The status step now also resolves it
independently as a fallback, in case the score step never ran at all.
@PiotrRogulski
PiotrRogulski merged commit e9f138c into master Aug 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants