ci: skip forwarded sync activity

This commit is contained in:
Peter Steinberger 2026-05-03 22:20:15 +01:00
parent 3ef87d364a
commit 460bb0dd35
No known key found for this signature in database
3 changed files with 10 additions and 9 deletions

View File

@ -65,6 +65,7 @@ jobs:
if: >-
${{
!(github.event_name == 'pull_request_target' && github.event.action == 'synchronize') &&
!(github.event_name == 'repository_dispatch' && github.event.client_payload.activity.type == 'pull_request_target' && github.event.client_payload.activity.action == 'synchronize') &&
!(github.event_name == 'workflow_run' && contains(fromJSON('["success","neutral","skipped"]'), github.event.workflow_run.conclusion))
}}
runs-on: blacksmith-4vcpu-ubuntu-2404

View File

@ -19,8 +19,8 @@ checkpoint, and status-only commits are intentionally omitted.
- Removed `actions/setup-node` from the high-volume GitHub activity lane and
kept that notifier compatible with runner-provided Node 20+ so bursty
activity forwarding is not blocked by codeload action download timeouts.
- Skipped routine pull request synchronize events and successful workflow-run
events before checkout in the GitHub activity lane.
- Skipped routine native and forwarded pull request synchronize events plus
successful workflow-run events before checkout in the GitHub activity lane.
- Kept human-review pauses from being cleared by stale trusted pass markers or
replayed automerge commands.
- Updated targeted re-review command comments with live progress while the review

View File

@ -186,13 +186,13 @@ default. The agent receives the Discord target in the prompt and should use the
message tool only when the event is surprising, actionable, risky, or otherwise
operationally useful. For routine events it replies exactly `NO_REPLY`.
The workflow skips pull request synchronize events and successful workflow-run
events before checkout because the notifier always treats them as routine. The
notifier also applies a cheap deterministic prefilter before calling OpenClaw.
Routine bot comments, comment edits, metadata edits, duplicate PR synchronizes,
and successful automation events are skipped unless they contain an explicit
ClawSweeper command or mention. This keeps noisy GitHub churn from consuming
hook-session model turns.
The workflow skips native and forwarded pull request synchronize events plus
successful workflow-run events before checkout because the notifier always
treats them as routine. The notifier also applies a cheap deterministic
prefilter before calling OpenClaw. Routine bot comments, comment edits, metadata
edits, duplicate PR synchronizes, and successful automation events are skipped
unless they contain an explicit ClawSweeper command or mention. This keeps noisy
GitHub churn from consuming hook-session model turns.
The workflow intentionally uses the runner-provided Node runtime plus a lean
uncached pnpm install instead of `actions/setup-node` or the shared cached pnpm