Approve customer patch workflow runs
Remove a manual queue from urgent customer patch delivery.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Approve a workflow run for a fork pull request
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Why this helps
A patch can be ready while its fork workflow waits for someone to approve it.
- Faster patch validation
- Less queue watching
- Clear approval records
Setup
Build it in a few focused steps.
- 1Connect Close and GitHub in Notis once.
- 2Create a new automation in Automations.
- 3Tell Notis to approve the waiting workflow run for each eligible fork pull request listed in the Close patch queue.
- 4Choose a recurring schedule and a report channel.
- 5Test with one real customer patch.
Questions about this workflow
Does this approve every fork workflow?
Limit the prompt context to the specific pull requests and runs that are eligible.
What if approval is not required?
GitHub returns the current result and the run report records it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Close to GitHub. A trigger fires from one place; an action lands in another.
Close 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.
Close 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.