Check whether the pull request for a browser fix has merged
Use a recurring Browserbase review to revisit a known browser issue and check the supplied GitHub pull request's merge status.
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
After reporting a browser bug, it is easy to lose track of whether the proposed fix has landed.
- Revisit browser issue evidence on a schedule.
- Check merge status for the supplied pull request.
- Keep follow-up connected to the original browser finding.
Setup
Build it in a few focused steps.
- 1Connect Browserbase and GitHub once in Notis.
- 2Create an automation in plain language or in Automations, New Automation.
- 3In one instruction, ask Notis to review the scheduled browser check and check whether the supplied fix pull request has merged.
- 4Choose a recurring schedule as the trigger.
- 5Choose a run report destination, then test with one real browser finding and its pull request.
Questions about this workflow
Will this find or create the pull request?
No. Supply the repository and pull request details as context; this action checks whether that pull request has merged.
What happens if it has not merged?
Notis can report the status so you can follow up. The available action only checks merge status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserbase tool to GitHub. A trigger fires from one place; an action lands in another.
Browserbase tool 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.
Browserbase tool 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.