Confirm the code change before the release moment
Replace launch-day uncertainty with one dependable status check.
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
Release pages and code repositories can drift out of sync when several people are moving quickly.
- Catches release readiness gaps early
- Avoids manual pull request hunting
- Creates a clear checkpoint for launch decisions
Setup
Build it in a few focused steps.
- 1Connect Wachete and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: At the release checkpoint, check whether the GitHub pull request associated with the monitored release has merged and report any mismatch.
- 4Pick a recurring schedule, choose the channel for run reports, and test with one real pull request.
Questions about this workflow
What if the pull request is not merged?
Notis reports that the release checkpoint is not yet satisfied.
Can I run this only during launch week?
Yes. Choose a schedule that matches the release window.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Wachete to GitHub. A trigger fires from one place; an action lands in another.
Wachete triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Wachete and GitHub. Any 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.