🔧 Add force-build-status-execution label trigger to CI workflow#6787
Conversation
Allow manually re-triggering the Build Status workflow by adding the "force-build-status-execution" label to a PR. The label is automatically removed once the workflow starts, making it a toggle mechanism. https://claude.ai/code/session_01GvBFqpr2tLmtAinffaPfNk
…action list Move the pull-requests:write permission from workflow-level into the remove_force_label job only. Replace negated != 'labeled' conditions with explicit listing of all expected actions (push, opened, synchronize, reopened, labeled with correct name). https://claude.ai/code/session_01GvBFqpr2tLmtAinffaPfNk
The new remove_force_label job and explicit if conditions added 21 lines, shifting all subsequent line references. https://claude.ai/code/session_01GvBFqpr2tLmtAinffaPfNk
|
|
👋 It looks like the PR template was not used for this pull request. Please edit the PR description to use the template, or close this PR and open a new one that uses it. The template includes:
Thank you for your contribution! 🙏 |
|
@claude fix the merge conflict with main on zizmor |
|
Claude finished @dubzzz's task in 4m 3s —— View job Fixing merge conflict with main on zizmor
Updated the Line number changes:
The Note: The |
Update cache-poisoning line numbers to account for both the 21 lines added by this PR and the changes made on main (release workflow settings, packaged commands, codecov update). Co-authored-by: Nicolas DUBIEN <[email protected]>
@fast-check/ava
fast-check
@fast-check/jest
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6787 +/- ##
=======================================
Coverage 94.52% 94.52%
=======================================
Files 210 210
Lines 5685 5685
Branches 1498 1498
=======================================
Hits 5374 5374
Misses 298 298
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@claude update zizmor whitelist |
|
Claude finished @dubzzz's task in 1m 12s —— View job Updating zizmor whitelist
Updated all line numbers in
|
Description
This PR enhances the build-status workflow to support manual triggering via a GitHub label, enabling developers to force a rebuild without pushing new commits.
Changes Made
Extended pull_request trigger types: Added
opened,synchronize,reopened, andlabeledevent types to the pull_request trigger configuration, allowing the workflow to respond to label additions.New
remove_force_labeljob: Added a dedicated job that automatically removes theforce-build-status-executionlabel after it triggers the workflow, keeping the PR clean and preventing accidental re-triggers.Conditional job execution: Updated
warmup_pnpm_cacheandwarmup_pnpm_cache_othersjobs with conditional logic to run when:force-build-status-executionlabel is added (new behavior)Updated security configuration: Adjusted line numbers in
.github/zizmor.ymlto reflect the new workflow structure (21 lines added).Motivation
This allows developers to manually trigger the build status workflow on existing PRs without making unnecessary commits, improving the development experience when debugging CI issues or re-running checks after external dependencies are fixed.
Checklist
https://claude.ai/code/session_01GvBFqpr2tLmtAinffaPfNk