Build coding habits in Habitica with GitHub

Every Octogriffin trigger is a Habitica habit that gets scored when something happens on GitHub. These recipes are ready-made triggers you can add to your dashboard in one click to reward the coding habits you want to keep.

Recipes

Trivial

Code a little every day

Scores once per commit you push, so a small reward keeps big pushes from flooding your character with Gold.

When push happens, score “Pushed code” as a Trivial habit and reward you. The counter resets daily. Empty commits don't count.

Easy

Ship pull requests

Rewards finishing work and putting it up for review, not just typing.

When pull_request.opened happens, score “Opened a pull request” as an Easy habit and reward you. The counter resets weekly.

Medium

Review your teammates' code

Code reviews are easy to put off. A bigger reward makes them worth picking up.

When pull_request_review.submitted happens, score “Reviewed a pull request” as a Medium habit and reward you. The counter resets weekly.

Easy

Close out issues

Keeps your backlog shrinking instead of only growing.

When issues.closed happens, score “Closed an issue” as an Easy habit and reward you. The counter resets weekly.

Hard

Ship a release

Releases are rare and hard-won, so they get the biggest reward.

When release.published happens, score “Published a release” as a Hard habit and reward you. The counter resets monthly.

Tips

  • Reuse a habit you already have. Octogriffin looks for a Habitica task with exactly the same title before creating a new one. For a perfect match, set the Task Alias under Advanced Settings.
  • Difficulty sets the size of the reward. Harder habits give more XP and Gold per score, so save Medium and Hard for things that don't happen often.
  • Reset Counter decides whether Habitica counts the habit per day, week or month.
  • Split work and side projects. Create two triggers for the same event with different repositories and task titles to see each one as its own habit.
  • Use "Punish" carefully. Some events fire for good and bad outcomes alike, for example a workflow run that passed or failed. Check the supported GitHub events before taking away health.
Something went wrong?
Open an Issue on GitHub →