Contributor profiles
Make the value you shipped easier to see.
A contributor profile turns accepted repository work into a portable record of Contributor Value, durability, technical range, streaks, badges, and evidence you can open.
The developer controls what becomes public. Private repository names, source, clients, and contribution details stay hidden unless their owner allows them.
Your work should not disappear inside repositories other people own.
The profile connects attributed accepted work to the repositories, evidence, retention checks, and technical areas behind it. It gives a developer a useful record without pretending that one software metric captures judgment, mentorship, leadership, or total professional value.
The result is only useful if you can see what produced it.
Accepted contribution value
Maps accepted changes to a verified contributor identity and conserves shared credit across authors, co-authors, and mapped delivery evidence.
How value was delivered
Separates capability created, value protected, complexity retired, and enablement so useful deletion and verification work remain visible.
What remained
Later repository checks update whether accepted work remains, was rewritten, or was reversed instead of treating the first receipt as permanent.
Accepted ship streaks
Counts calendar-day and configured-workday streaks only when accepted work with nonzero value reaches the tracked branch.
Repositories and technical areas
Shows the languages, systems, repositories, and contribution types evidenced by the work the developer chooses to include.
Profile visibility
Lets the verified developer hide values, exclude repositories, keep the page unlisted, make it private, or remove the public profile.
From repository evidence to a readable record.
Verify the GitHub identity
Use GitHub authorization to match the account to its durable actor ID, even if the username changes later.
Choose repository access
Select public and approved private repositories, then review the attributed accepted work and evidence coverage.
Publish only what you choose
Control the repositories, aggregate private work, values, badges, milestones, and profile visibility before sharing.
One evidence base, read from the right perspective.
Carry a record of accepted work between teams.
Use the profile to revisit what shipped, what endured, and the technical range evidenced across repositories.
- Verified contributor identity
- Repository evidence behind the value
- Developer-controlled public visibility
Open the evidence behind the profile.
Use the record as one input alongside role expectations, product outcomes, mentorship, judgment, and work Git cannot observe.
- Accepted delivery instead of activity volume
- Durability and shared-credit context
- Explicit measurement boundaries
Clear evidence boundaries are part of the product.
Contributor Value estimates accepted software delivery. It does not measure the worth, potential, judgment, or complete contribution of a person.
The profile does not replace role context, customer outcomes, leadership, mentorship, discovery, incident work, or manager judgment.
Private details are not made public by default, and the verified developer controls whether a public profile is listed or available at all.
Questions
What to know before publishing a contributor profile.
The verified developer controls the profile, its visibility, and the private evidence that stays out of it.
How is a contributor profile verified?
GitHub authorization maps the account to its durable GitHub actor ID. That identity can remain stable even if the visible username changes later.
Does the profile include every kind of contribution?
No. It records accepted repository work the system can attribute and measure. Product judgment, mentorship, leadership, planning, customer work, incident response, and other non-repository contributions require separate context.
Can private work appear without naming the repository?
Yes. The developer can keep private work hidden or share approved aggregates without exposing repository names, clients, source code, or individual contribution details.
Who decides whether the profile is public?
The verified developer controls whether the profile is private, unlisted, or public and which repositories, values, badges, and milestones appear. Connecting GitHub does not automatically publish the profile.
Build the record
Let accepted work compound into proof.
Connect GitHub, choose the repositories you can authorize, and review the evidence before deciding what to share.