Keep GitHub issue ownership up to date
Describe how available issue context should guide ownership, then have Notis update assignees during a recurring review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Issues can sit without a clear owner when assigning or adjusting responsibilities depends on a manual review.
- Review ownership on a cadence that fits your team.
- Apply assignment guidance in one plain language instruction.
- Add or remove issue assignees based on the context available to Notis.
Setup
Build it in a few focused steps.
- 1Connect Celigo and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3Describe how issue context should guide adding or removing assignees in one instruction.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real example and confirm the report.
Questions about this workflow
What information should I provide for assignment decisions?
State the ownership rules Notis should use and ensure the relevant issue context is available. If a rule depends on information GitHub does not return, provide that information in your instruction or request.
Can this action change assignees both ways?
Yes. The GitHub action supports adding or removing assignees. Tell Notis which changes to make for the cases you describe.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Celigo to GitHub. A trigger fires from one place; an action lands in another.
Celigo 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.
Celigo 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.