Automatic developer check-ins

GitHub habit tracker integration

Set a daily target for commits, pull requests, or code reviews. Main Character checks in the habit when your GitHub contribution count reaches it.

CommitsPull requestsCode reviewsDaily targets

Best for

Habits where this source is useful.

  • Shipping code consistently
  • Opening pull requests instead of leaving branches unfinished
  • Building a regular code review habit

Check-in examples

What can count as a check-in.

  • Check in a coding habit after your first commit of the day.
  • Complete a shipping habit when you open a pull request.
  • Track a review habit with a daily code review target.

How it works

From source signal to habit check-in.

  1. 01

    Connect GitHub and approve the read:user permission.

  2. 02

    Choose commits, pull requests, or code reviews and set a daily target.

  3. 03

    Main Character reads the aggregate contribution count for the day.

  4. 04

    The habit checks in when the count reaches your target. Manual check-ins stay available.

Privacy boundaries

Your data stays scoped.

  • Main Character requests GitHub's read:user scope for this connection.
  • It reads and stores daily contribution counts, not repository names, commit messages, code, diffs, issues, or organization membership.
  • Disconnecting removes imported GitHub totals, automatic check-in settings, and supporting data. Existing check-ins remain in your history.

FAQ

Common questions.

Which GitHub activity can automate a check-in?

Main Character supports daily counts for commits, pull requests, and code reviews.

Can Main Character read my repositories or code?

No. The integration requests aggregate contribution counts. It does not request repository names, commit messages, code, diffs, issues, or organization membership.

Who can connect GitHub right now?

GitHub automatic check-ins are in early access. The integration appears in the app for accounts included in the current rollout.