Skip to content
Merged notification

Repo sync #22012

Sign in to view logs

Repo sync

Repo sync #22012

Workflow file for this run

.github/workflows/merged-notification.yml at 6167d14
name: Merged notification

Check warning on line 1 in .github/workflows/merged-notification.yml

View workflow run for this annotation

GitHub Actions / Merged notification

Workflow execution policy warning (evaluate mode) 

On November 2, 2026, GitHub will restrict `pull_request_target` on public repositories by default. To continue allowing the event trigger, configure an Actions policy. Learn more: https://gh.io/securely-using-pull_request_target#default-policy-for-pull_request_target
# docs-internal deploys docs, so merged public PRs need a production timing notice.
on:
# pull_request_target lets this workflow comment on pull requests from forks.
pull_request_target:
types:
- 'closed'
permissions:
issues: write
pull-requests: write
contents: read
jobs:
comment:
if: github.repository == 'github/docs' && github.event.pull_request.merged && github.event.pull_request.base.ref == github.event.repository.default_branch && github.event.pull_request.user.login != 'docs-bot'
runs-on: ubuntu-latest
steps:
- uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3
with:
script: |
github.rest.issues.createComment({
...context.repo,
issue_number: context.payload.pull_request.number,
body: "Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our [help wanted issues](https://github.com/github/docs/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) :zap:"
})