Keep monthly release actions owned in GitHub
Use your recurring release review to make sure referenced GitHub actions have the owners named in the checklist.
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
Release actions can remain open without an owner when the checklist and GitHub issue tracker are reviewed separately.
- Revisit release action ownership each month.
- Use the checklist's explicit owner information.
- Keep related GitHub issues moving.
Setup
Build it in a few focused steps.
- 1Connect CloudPDF and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to review the release checklist context available to it and assign each referenced GitHub issue to the owner explicitly named in the checklist.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one checklist and a known issue.
Questions about this workflow
Can Notis assign an owner if the checklist is vague?
No. Ask it to report unclear or missing owner information instead of guessing.
Does the workflow pull checklists from CloudPDF?
No source fetch action is listed. The relevant checklist context must be made available to Notis for the scheduled run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CloudPDF to GitHub. A trigger fires from one place; an action lands in another.
CloudPDF 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.
CloudPDF 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.