Repository navigation
ci: probe checks on edited (if) - #7
christianhg wants to merge 4 commits into
Conversation
…d `Checks` workflow The five check workflows move into one `checks` job that calls `checks.yml` in `portabletext/.github`, so the required checks become `checks / commits`, `checks / format`, `checks / lint`, `checks / types` and `checks / knip`. The commit check gains one rule: a commit whose subject is not `fix:` or `feat:` fails when it adds a changeset.
Bundle Stats✅ No significant changes. All scenario measurements (1)🗺️ View treemap · Artifacts
Significant means at least 1.0 KB and 1% gzip, or at least 5 ms and 10% import time. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7c213f4. Configure here.
| jobs: | ||
| checks: | ||
| # Base changes alter the commit set that needs checking. | ||
| if: github.event.action != 'edited' || github.event.changes.base |
There was a problem hiding this comment.
Skipped checks can hide failures
Medium Severity
A title or body edit retriggers this workflow and the job-level if skips checks. GitHub treats skipped jobs as success, so that run can replace a failed required check on the same head SHA and leave a previously red PR mergeable.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 7c213f4. Configure here.


Throwaway probe of required checks after a PR edit. Closed without merging. (edited)