Check whether project pull requests have merged
Let Notis check linked GitHub pull requests on a schedule and report the merge status alongside Bonsai project work.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Project follow-up depends on repeatedly checking GitHub to see whether a change has merged.
- Surface merge status during routine project reviews
- Reduce repeated context switching between Bonsai and GitHub
- Keep follow-up focused on pull requests that still need attention
Setup
Build it in a few focused steps.
- 1Connect Bonsai and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, tell Notis to review Bonsai projects with GitHub pull request references, check whether each pull request is merged, and report the result.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real project and pull request reference.
Questions about this workflow
Does this close or update the Bonsai project?
No. The selected GitHub action checks merge status. Use the run report to inform follow-up.
What information does a project need?
Notis needs a GitHub repository and pull request reference for each item it should check.
Can it report only unmerged pull requests?
You can instruct Notis to highlight unmerged items in its report. The action checks the merge state of each specified pull request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bonsai to GitHub. A trigger fires from one place; an action lands in another.
Bonsai 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.
Bonsai 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.