Close the loop after every release
A release is not complete until the code change is confirmed.
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 checklists linger because nobody is certain whether every pull request landed.
- Prevents incomplete release follow-up
- Makes release status easier to trust
- Reduces repeated checking
Setup
Build it in a few focused steps.
- 1Connect New Relic and GitHub to Notis once through the portal.
- 2Create a recurring automation in the portal or ask Notis to create it conversationally.
- 3Instruct Notis to use New Relic release context and check whether each named GitHub pull request has merged.
- 4Pick a cron trigger and a channel for run reports.
- 5Test with one recently released pull request.
Questions about this workflow
What happens if a pull request is not merged?
Notis reports the result in the selected channel so you can act on it.
Can this run after each deployment window?
Yes. Choose a schedule aligned with your release cadence.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link New relic to GitHub. A trigger fires from one place; an action lands in another.
New relic 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 New relic and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.