Catch commute disruptions in your GitHub issue list
Let Notis check your chosen Bart route on a schedule and mark the related GitHub issue when an alert affects it.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
A disruption that starts overnight or between check-ins can be easy to miss before the workday begins.
- Check a regular route without remembering to do it
- Make affected work visible in GitHub
- Keep a simple record of commute-related disruptions
Setup
Build it in a few focused steps.
- 1Connect Bart and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3In one instruction, describe the Bart route and existing GitHub issue to check and label when service is disrupted.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real service alert and the related issue.
Questions about this workflow
What schedule should I use?
Choose a recurring schedule that fits when you need the route checked. The workflow checks for Bart alerts when it runs.
What does GitHub need to contain first?
The issue must already exist. Tell Notis how to identify it, such as its repository and issue number or another clear reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bart to GitHub. A trigger fires from one place; an action lands in another.
Bart 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.
Bart 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.