Verify the GitHub change behind an Appcircle deployment
When deployment context includes a pull request reference, Notis can check its merge status and report the result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Deployment reports can arrive without an easy answer to whether the corresponding GitHub change was merged.
- Checks merge status when deployment context arrives
- Keeps the result attached to the deployment follow-up
- Avoids a separate manual GitHub lookup
Setup
Build it in a few focused steps.
- 1Connect Appcircle and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to read the pull request reference in an Appcircle deployment report and check whether that pull request has merged.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one real deployment report containing a pull request reference.
Questions about this workflow
What if the report has no pull request reference?
Instruct Notis to report that the reference is missing and skip the merge check.
Does a successful check change the pull request?
No. The action only checks whether the specified pull request has merged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Appcircle to GitHub. A trigger fires from one place; an action lands in another.
Appcircle 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.
Appcircle 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.