Keep a GitHub issue assigned from an Ascora update
When an operations update points to an engineering issue, pass the issue and assignee details to Notis and let GitHub reflect the handoff.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A job update can leave an engineering issue without a clear owner when assignment details have to be copied by hand.
- Reduce manual issue assignment after an Ascora job update.
- Keep issue and assignee details with the webhook request.
- Make ownership changes visible in GitHub.
Setup
Build it in a few focused steps.
- 1Connect Ascora and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to use the repository, issue number, and GitHub username in an Ascora webhook request to update the issue's assignees.
- 4Choose the notis_webhook trigger and where run reports should go.
- 5Test with one real request for an issue and an assignable GitHub user.
Questions about this workflow
Can this workflow find a GitHub issue from an Ascora job by itself?
Only if the webhook request provides the repository and issue number or you supply a reliable way to identify them.
What if the GitHub user cannot be assigned?
GitHub may ignore the change when the authenticated user lacks push access, or reject an invalid assignment. Check the run report and repository permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ascora to GitHub. A trigger fires from one place; an action lands in another.
Ascora 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.
Ascora 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.