Skip to content

feat(marketing): include co-authors in contributors strip#662

Merged
backnotprop merged 3 commits intomainfrom
feat/marketing-contributors-include-co-authors
May 5, 2026
Merged

feat(marketing): include co-authors in contributors strip#662
backnotprop merged 3 commits intomainfrom
feat/marketing-contributors-include-co-authors

Conversation

@backnotprop
Copy link
Copy Markdown
Owner

Summary

  • Parses Co-authored-by: trailers from commit messages (already fetched via GraphQL) to extract co-author emails
  • Resolves emails to GitHub profiles via /search/users so co-authors of squash-merged PRs appear on the homepage
  • Preserves the existing recency-based ordering (Map insertion order from most-recent commits first)

Fixes the case where contributors like @gjermundgaraba (co-author on #652) were invisible because GitHub's GraphQL Commit.author only returns the primary author.

Test plan

  • Run GITHUB_TOKEN=$(gh auth token) bun run dev:marketing and verify co-authors appear in the contributors strip at the bottom of the homepage
  • Verify ordering matches the previous most-recent-first behavior
  • Verify the unauthenticated fallback (no token) still works

Parse Co-authored-by trailers from commit messages and resolve emails
to GitHub profiles via /search/users, so co-authors of squash-merged
PRs appear in the contributors strip.
Split the contributors strip into two sections: "Built by" for commit
authors and co-authors, "With contributions from" for issue/discussion
participants. Also use REST /contributors for full commit history
coverage and parse GitHub noreply emails for co-author resolution.
Paginate through the full commit history via GraphQL so Co-authored-by
trailers in older commits are not missed. Also handle the login-only
noreply email format (login@users.noreply.github.com) in addition to
the id+login form.
@backnotprop backnotprop merged commit 61e44ef into main May 5, 2026
10 checks passed
@backnotprop backnotprop deleted the feat/marketing-contributors-include-co-authors branch May 5, 2026 05:11
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