Keep an eye on Authyo release pull requests
Schedule a lightweight check on a known GitHub pull request so its merge status is easier to track.
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
A release checklist can linger when nobody remembers to revisit the pull request status.
- Revisit a specified pull request on a recurring schedule.
- Make merged or not-yet-merged status easier to see in run reports.
- Reduce the need to repeatedly open GitHub for a known release change.
Setup
Build it in a few focused steps.
- 1Connect Authyo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3Tell Notis to check the merge status of the GitHub pull request reference you provide.
- 4Choose the notis_cron trigger and set its recurring schedule, then choose a report channel.
- 5Test with one real pull request reference.
Questions about this workflow
Does Authyo provide the pull request reference?
No. Authyo has no trigger events here, and the scheduled workflow needs the GitHub pull request reference in its instruction or available context.
What does this check report?
The GitHub action checks whether the specified pull request has been merged. It does not merge or modify the pull request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Authyo to GitHub. A trigger fires from one place; an action lands in another.
Authyo 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.
Authyo 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.