NIGHT: Developer Commits by Repository
The daily developer commits split by repository.
Why use it. Shows which parts of the project carry the work: node clients, protocol specifications, contracts or SDKs. How to read it. Each band is one repository and the bands add up to the daily commits. A change found in several repositories appears under the one listed first that holds its earliest copy. A repository appears from its first counted commit.
Calculation. Non-merge commits on each repository's default branch (and the branches named below). The history found when we began mirroring a repository (19 October 2026 for every current one) is dated by each commit's author timestamp in UTC: when the change was written, which rebases, cherry-picks and copies into other repositories keep. Since then a new commit is dated when it reached the branch: the time of the merge that brought it in, or its own time when added directly, held between our previous fetch and the fetch that found it, so a day already observed is never revised. A change counts once for the asset: copies in several of its repositories (forks, mirrors, cherry-picks, rewritten histories) are recognised by the same commit or the same author at the same second and count on the earliest date. Commits by automation accounts are left out: GitHub Apps (names ending in "[bot]"), known accounts such as Dependabot, Renovate and GitHub Actions, and names or GitHub accounts that contain the word "bot" or end in "Bot". The open day is partial; a closed day is final once our next fetch has run. Source: CryptoKeyhole's own mirrors of 2 public repositories of Midnight on GitHub, fetched every 30 minutes. midnightntwrk/midnight-node: the Midnight node. midnightntwrk/midnight-ledger: the Midnight ledger. History starts at the first counted commit, on 30 July 2024. Only public repositories are covered: work in private repositories, on other hosts or on branches not yet merged is not seen.