See device check status beside pull request merge status
Put two operational signals in one scheduled run report: Bolt IoT check data and the merge status of specified pull requests.
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
Checking device results and pull request status in separate places makes routine release follow-up easy to postpone.
- Review device signals and pull request status in one automation run.
- Get a report on whether specified pull requests have merged.
- Reduce context switching during routine release follow-up.
Setup
Build it in a few focused steps.
- 1Connect Bolt IoT and GitHub once in Notis.
- 2Create an automation from any channel or in Automations, New Automation.
- 3Tell Notis which device checks and pull requests to review and ask it to report merge status with the check results.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real device check and a pull request reference.
Questions about this workflow
Does this merge pull requests?
No. The available GitHub action checks whether a specified pull request has already merged.
Can the workflow infer which pull requests to check?
Provide the pull request references in the automation instruction or schedule context; the action does not provide a broad pull request listing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bolt iot to GitHub. A trigger fires from one place; an action lands in another.
Bolt iot 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.
Bolt iot 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.