v1.2.4

Fixed

• The contribution time zone is resolved once during setup through Home Assistant instead of being read from disk on the event loop. The options form validates it the same way.
• Diagnostics no longer contain the GitHub account name: the entry title, unique ID, owner, repository names, and the name, query, variables and templates of custom queries are redacted.

Full changelog: CHANGELOG.md

v1.2.3

Changed

• The README describes the installation through the HACS search instead of a custom repository, with an Open in HACS button. Adding the repository by hand stays documented as a fallback.

Full changelog: CHANGELOG.md

v1.2.2

[1.2.2] - 2026-10-27

Fixed

• The most active hour and night owl score sensors no longer alternate between two values. Paginated GitHub responses that were answered with 304 Not Modified lost their link to the next page, so every other refresh analysed only the newest 100 events instead of 300.

v1.2.1

[1.2.1] - 2026-10-27

Changed

• New custom query sensors get an entity ID with the same prefix as the account's other entities, for example sensor.github_octocat_followers instead of sensor.followers. Existing query entities keep their entity ID; rename them in the entity settings to match.

v1.2.0

[1.2.0] - 2026-10-26

Added

• Per repository: commits and active days on the default branch this month, and the change versus last month and last year (like for like, so a partial month is never compared with a full one).
• Per repository: pull requests and issues created this month.
• These counts include every author, unlike the account sensors, and come from the existing batched query, so tracking a repository still costs no extra request.

1.1.0

Added

• Adding repositories now offers a list of the most recently pushed repositories the token can read, with multi-select so several can be added at once. Typing a name still works, also when the list cannot be loaded.

Changed

• New integration icon: a blue badge with a lion that has gear eyes.

Fixed

• Adding a custom query no longer makes the account's other entities disappear. The query sensor used the account device, which Home Assistant then moved into the query's subentry. Query sensors now have no device, and an affected account device is moved back on startup. New query entities are named without the "GitHub " prefix; existing entity IDs are unchanged.

1.0.2

Changed

• The longest-streak sensor is now named "Longest streak (last year)", because it covers the one-year window GitHub allows per request. Existing entity IDs are unchanged.

1.0.1

Changed

• The setup form now states that a single token serves all modules and recommends a classic token with repo and read:org.
• A classic token without the repo scope now gets a notice during setup that private data stays invisible, instead of passing silently.

1.0.0

Added

• Workflow run tracking per repository: last result, runs today, queued runs, failure rate over 7 and 30 days, average duration and a running indicator.
• Event entities and event-bus events for failed and recovered workflows, published releases, review requests and merged pull requests, with deduplication across restarts.
• Automation blueprints for failed workflow runs and review requests.
• Custom queries: add your own read-only GraphQL query as a sensor. Queries are validated (single query, cost cap, minimum interval), test-run before saving, and rendered with templates over value_json.
• Optional rhythm sensors: most active hour and night-owl score, labelled approximate.
• Optional work-in-progress sensors: average time to merge and stale pull requests.
• Year in review: service github_pulse.year_in_review and an optional text sensor.
• German translation.
• CONTRIBUTING.md and a documentation pass.
• Preset queries as starting points for custom queries.
• Service github_pulse.query to run a read-only GraphQL query and get the result as a response.

0.1.0

First release. Profile statistics, estimated language usage, repository sensors, search-based pull request counts, opt-in long-term statistics and the get_history service. See CHANGELOG.md for details.