Skip to content

🔧 Add force-build-status-execution label trigger to CI workflow#6787

Merged
dubzzz merged 9 commits into
mainfrom
claude/add-pr-synchronized-event-2V3Tk
Mar 28, 2026
Merged

🔧 Add force-build-status-execution label trigger to CI workflow#6787
dubzzz merged 9 commits into
mainfrom
claude/add-pr-synchronized-event-2V3Tk

Conversation

@dubzzz

@dubzzz dubzzz commented Mar 27, 2026

Copy link
Copy Markdown
Owner

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

  1. Extended pull_request trigger types: Added opened, synchronize, reopened, and labeled event types to the pull_request trigger configuration, allowing the workflow to respond to label additions.

  2. New remove_force_label job: Added a dedicated job that automatically removes the force-build-status-execution label after it triggers the workflow, keeping the PR clean and preventing accidental re-triggers.

  3. Conditional job execution: Updated warmup_pnpm_cache and warmup_pnpm_cache_others jobs with conditional logic to run when:

    • A push event occurs (existing behavior)
    • A PR is opened, synchronized, or reopened (existing behavior)
    • The force-build-status-execution label is added (new behavior)
  4. Updated security configuration: Adjusted line numbers in .github/zizmor.yml to 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

  • I have a full understanding of every line in this PR
  • This is a minor change to CI/workflow configuration
  • The change is focused on a single concern (adding label-based workflow trigger)
  • Followed gitmoji specification for PR title

https://claude.ai/code/session_01GvBFqpr2tLmtAinffaPfNk

claude added 3 commits March 27, 2026 13:10
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
@changeset-bot

changeset-bot Bot commented Mar 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 633280b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

👋 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.
Not using the template may result in your change not being reviewed.

The template includes:

  • A Description section
  • A Checklist section with items to verify before submitting

Thank you for your contribution! 🙏

@dubzzz

dubzzz commented Mar 27, 2026

Copy link
Copy Markdown
Owner Author

@claude fix the merge conflict with main on zizmor

@claude

claude Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

Claude finished @dubzzz's task in 4m 3s —— View job


Fixing merge conflict with main on zizmor

  • Fetch latest main and identify conflict
  • Resolve merge conflict in .github/zizmor.yml
  • Push resolved changes

Updated the cache-poisoning line numbers in .github/zizmor.yml to account for both this PR's +21 lines at the top of build-status.yml and the changes merged into main since this branch was created (release workflow settings from #6786, packaged commands, codecov update).

Line number changes:

Package Old (branch) New (merged)
fast-check 630 626
ava 705 703
jest 780 780
packaged 855 857
poisoning 930 934
vitest 1005 1011
worker 1080 1088

The use-trusted-publishing lines (231, 234) remain correct.

Note: The build-status.yml workflow file also has differences with main (release settings, packaged commands, codecov version), but those changes are in different sections and should merge cleanly. I'm unable to modify workflow files due to GitHub App permissions — those conflicts will need to be resolved separately if GitHub reports them.

github-actions Bot and others added 2 commits March 27, 2026 16:06
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]>
@pkg-pr-new

pkg-pr-new Bot commented Mar 27, 2026

Copy link
Copy Markdown
@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@6787

fast-check

npm i https://pkg.pr.new/fast-check@6787

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@6787

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@6787

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@6787

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@6787

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@6787

commit: 633280b

@codecov

codecov Bot commented Mar 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.52%. Comparing base (f8e25f6) to head (633280b).
⚠️ Report is 1 commits behind head on main.

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           
Flag Coverage Δ
tests 94.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread .github/workflows/build-status.yml Outdated
@dubzzz

dubzzz commented Mar 28, 2026

Copy link
Copy Markdown
Owner Author

@claude update zizmor whitelist

@claude

claude Bot commented Mar 28, 2026

Copy link
Copy Markdown
Contributor

Claude finished @dubzzz's task in 1m 12s —— View job


Updating zizmor whitelist

  • Read current workflow and zizmor files
  • Determine correct line numbers
  • Update .github/zizmor.yml
  • Commit and push changes

Updated all line numbers in .github/zizmor.yml to reflect the removal of the remove_force_label job (18 lines removed):

Entry Old New
use-trusted-publishing (pkg-pr-new) 231, 234 213, 216
cache-poisoning: fast-check 626 608
cache-poisoning: ava 703 685
cache-poisoning: jest 780 762
cache-poisoning: packaged 857 839
cache-poisoning: poisoning 934 916
cache-poisoning: vitest 1011 993
cache-poisoning: worker 1088 1070

@dubzzz
dubzzz merged commit 2133f2e into main Mar 28, 2026
51 checks passed
@dubzzz
dubzzz deleted the claude/add-pr-synchronized-event-2V3Tk branch March 28, 2026 11:36
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