Check the merge status behind a BunnyCDN deployment signal
A CDN deployment signal can be easier to act on when the associated GitHub pull request's merge status is checked and reported in the same run.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
Deployment notes and code review status can live in separate places, making it easy to assume a change is complete without checking the pull request.
- Check a specific pull request during deployment follow-up.
- Reduce manual switching between CDN and repository context.
- Get a report with the check result.
Setup
Build it in a few focused steps.
- 1Connect BunnyCDN and GitHub once in Notis.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to use the pull request reference provided with the BunnyCDN webhook to check whether it merged, then report the result.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real deployment example and verify the pull request reference and result.
Questions about this workflow
Does a BunnyCDN deployment event trigger this directly?
No BunnyCDN trigger event is supplied. Use a Notis webhook and send it the deployment context and GitHub pull request reference.
What does the GitHub check return?
The action checks whether the specified pull request has merged. A 204 response indicates merged; a 404 indicates not merged or not found.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bunnycdn to GitHub. A trigger fires from one place; an action lands in another.
Bunnycdn triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Bunnycdn and GitHub, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.