Skip to content

chore(analytics): refresh public contributor participation - #1598

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
chore/update-contributor-metrics
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
chore/update-contributor-metrics

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Refreshes the complete public GitHub participation snapshot. Known bots and imported fork commit history are excluded; failed collection preserves last-good history and marks unavailability. Requires maintainer approval before merge.

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: This is the automated nightly refresh of the public contributor-activity snapshot that powers the analytics page. It only moves ten timestamps forward (the generation time and nine contributors' "last active" dates); no names are added or removed and no code changes. Nothing blocks it.


intent-alignment

  • (out-of-scope, info) The PR body says "known bots ... are excluded", but static/data/contributor-metrics.json:2254-2257 still carries codecov-commenter as a contributor (its lastContributionAt is one of the nine bumps). The entry pre-exists this PR; whether it belongs on the generator's bot list is a question for scripts/fetch-contributor-metrics.js, which I could not open this run (GitHub API quota exhausted). Not a blocker for this refresh.

No findings from: correctness, security, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Hive filed review findings that do not block this PR as backlog items:

Cap: 10 backlog item(s) per PR per day.

@hivecommons-hive

Copy link
Copy Markdown
Contributor

Another agent tried to open a PR from scanner/fix-1601, but this PR edits an overlapping set of files. No second PR was opened; please continue here, or rebase the new work onto this branch.

@github-actions
github-actions Bot force-pushed the chore/update-contributor-metrics branch from b2fa107 to 84aac63 Compare October 26, 2026 02:30

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary: This is the automated daily refresh of the contributor-participation numbers shown on the docs site. The new data is internally consistent (the per-person list adds up to the totals it reports), so it is safe to merge. One pre-existing wrinkle noted below for later: two automated accounts are still being counted as people, but this refresh did not cause that.


intent-alignment

  • (out-of-scope, pre-existing) The PR body says "known bots … are excluded", but codecov-commenter (static/data/contributor-metrics.json:2256) and ImgBotApp are counted as contributors in both base and head. They are User-typed accounts, so the __typename === "Bot" check (scripts/fetch-contributor-metrics.js:70) misses them, and neither matches BOT_PATTERNS (scripts/lib/contributor-tracker.mjs:18-30). Adding /^codecov-commenter$/ and /^ImgBotApp$/ there would fix it in a follow-up; not a blocker for this refresh.

Verified for this refresh: contributors[] length 457 = summary.totalContributors; 149 entries with lastContributionAt within 90d of generatedAt = summary.activeContributors90d; months[2026-10].cumulativeContributors 457 matches.

No findings from: correctness, security, style, docs-currency.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88

@Danathar

Copy link
Copy Markdown
Contributor

Closing: this refresh still counts codecov-commenter as a contributor, which #1602 excludes. The next scheduled run after #1602 merges will regenerate it correctly.

@Danathar Danathar closed this Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant