Give off-track Beeminder goals a GitHub owner
When progress slips, make the next step easier to see. Notis checks goals on a schedule and assigns the corresponding GitHub issue for follow-up.
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
Noticing a goal is off track does not help if nobody is clearly responsible for the next step.
- Put ownership next to the issue that needs attention.
- Catch follow-up needs in a regular review.
- Avoid repeatedly checking two tools for stalled work.
Setup
Build it in a few focused steps.
- 1Connect Beeminder and GitHub once in the Notis portal.
- 2In Automations, choose New Automation and give it a name and prompt.
- 3Tell Notis to check Beeminder progress and assign the corresponding GitHub issue when a goal is off track.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real off-track goal and the issue that tracks its work.
Questions about this workflow
Will this assign an issue for every Beeminder goal?
The instruction should define which goals need follow-up and how to find their corresponding GitHub issues.
Can Notis decide who owns the work?
Specify the intended assignee in your instruction or ensure the needed ownership information is available. Notis cannot infer a person or baseline that the connected data does not provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beeminder to GitHub. A trigger fires from one place; an action lands in another.
Beeminder 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.
Beeminder 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.