Keep an eye on the pull request for an Arize AX fix
Track a known fix pull request on a schedule and get a report of its merge status.
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
After an evaluation regression becomes a code fix, its pull request can be easy to forget amid other work.
- Keep a fix pull request on your radar
- Get a recurring status report
- Avoid repeatedly checking GitHub by hand
Setup
Build it in a few focused steps.
- 1Connect Arize AX and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, with the repository and pull request details for the Arize AX fix.
- 3Tell Notis to check whether that pull request has merged and report the result.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real pull request associated with an Arize AX evaluation fix.
Questions about this workflow
Does this workflow read evaluation data from Arize AX?
No. Arize AX trigger events are unavailable. This scheduled workflow checks a GitHub pull request that you identify as the fix for an evaluation finding.
What does the check report?
It reports whether the specified GitHub pull request is merged, based on GitHub's merge-status check.
Can it check multiple pull requests?
Use a separate automation for each pull request unless your prompt and connected GitHub capabilities support handling a list of pull requests.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Arize AX to GitHub. A trigger fires from one place; an action lands in another.
Arize AX 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.
Arize AX 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.