Skip to content

ci: post merge notices on pull_request, not pull_request_target - #25

Draft
gorandodig wants to merge 1 commit into
mainfrom
ci/slack-merge-on-pull-request
Draft

gorandodig wants to merge 1 commit into
mainfrom
ci/slack-merge-on-pull-request

Conversation

@gorandodig

Copy link
Copy Markdown
Member

GitHub will block pull_request_target in public repos by default from 2 December 2026, unless an Actions event policy allows it. This merge notifier would then stop posting, so it moves to pull_request (closed).

  • Merged PRs from forks get no secrets under pull_request, so the job now skips them instead of failing. Merges from branches in this repo post as before.
  • Under pull_request, the workflow file comes from the PR's merge ref rather than main. Only branches in this repo reach the step that uses the token.

GitHub blocks pull_request_target in public repos by default from
2 Dec 2026. Fork PRs get no secrets under pull_request, so their merges
are skipped instead of failing.
@coderabbitai

coderabbitai Bot commented Nov 3, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

CodeRabbit Verify

  • Run CodeRabbit Verify to test the changes in this pull request.

This branch has not been deployed

No deployments
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