Skip to content

feat: add paperclip-pr-notify with code-level event filtering#12

Closed
marvin-tensorleap wants to merge 1 commit into
masterfrom
ten-319-pr-notify
Closed

feat: add paperclip-pr-notify with code-level event filtering#12
marvin-tensorleap wants to merge 1 commit into
masterfrom
ten-319-pr-notify

Conversation

@marvin-tensorleap
Copy link
Copy Markdown
Collaborator

Why this change exists

Part of the TEN-302 GitHub↔TEN mapping architecture. New workflow applies deterministic code-level filtering before forwarding events to the Paperclip GitHub Event Router routine (TEN-319). Without filtering, every repository event would spawn a Paperclip agent.

How this PR fixes it

Only actionable events are forwarded to ${{ secrets.PAPERCLIP_WEBHOOK_URL }}:

  • check_suite: only completed + failure|timed_out|action_required + linked open PR present
  • pull_request: opened, closed, synchronize, reopened
  • pull_request_review: submitted with state approved or changes_requested
  • issues: opened, assigned, closed
  • issue_comment: created only

Payload is signed with HMAC-SHA256 (X-Hub-Signature-256 header).

Technical summary

  • New file: .github/workflows/paperclip-pr-notify.yml
  • Requires repo secrets: PAPERCLIP_WEBHOOK_URL, PAPERCLIP_WEBHOOK_SECRET

Verification

Once repo secrets are configured, open a draft PR (should forward) and add a label (should not forward).

Implements deterministic filtering for Paperclip GitHub Event Router.
Part of TEN-319 / TEN-302.
@marvin-tensorleap marvin-tensorleap self-assigned this May 5, 2026
@marvin-tensorleap
Copy link
Copy Markdown
Collaborator Author

Closing — this approach was superseded before merging. Paperclip plugin-based webhook dispatch handles event filtering locally. See TEN-319 and TEN-302.

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.

1 participant