Move trusted fork validation forward
Once the evidence is in, remove the manual approval pause from the right run.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Safe external contributions sit waiting because approval is disconnected from the completed validation evidence.
- Shortens safe contribution feedback loops
- Ties approval to explicit validation evidence
- Reduces repetitive approval checking
Setup
Build it in a few focused steps.
- 1Connect Databricks and GitHub to Notis once through the portal.
- 2Create a webhook automation telling Notis to approve the matching GitHub fork workflow run only when the Databricks validation service reports the defined trusted checks as passed.
- 3Give the validation service the Notis webhook URL and select the run-report channel.
- 4Test with one eligible fork pull request and confirm the approval target.
Questions about this workflow
Should every fork run be approved?
No. The prompt should include the repository, validation result, trust conditions, and matching pull request rules.
When is approval needed?
GitHub uses this action for fork workflow runs that require manual approval because of workflow configuration.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Databricks to GitHub. A trigger fires from one place; an action lands in another.
Databricks 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.
Databricks 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.