Retired GitHub achievements timeline
GitHub’s achievement system has changed over time. Some profile badges were tied to limited programmes, temporary events, or features that are no longer generally available.
How this timeline is classified
| Status | Meaning |
|---|---|
| Retired | Previously available but no longer generally earnable |
| Restricted | Available only through a limited programme, role, event, or historical condition |
| Historical | Preserved for reference, but current availability is not established |
| Unconfirmed | Reported by the community without sufficient dated evidence |
Historical entries
Arctic Code Vault Contributor
Classification: Historical / event-based
Context: Associated with GitHub’s 2020 Arctic Code Vault archival programme. The badge reflects qualifying contributions included in that archival snapshot rather than an ongoing achievement route.
Current expectation: It should not be presented as a badge that a new account can reproduce through current activity.
Mars 2020 Contributor
Classification: Restricted / historical
Context: Associated with contributions connected to software used by the Mars 2020 mission. It was not a general-purpose achievement with an ordinary repeatable trigger.
Current expectation: Treat as a historical recognition rather than an earnable profile objective.
GitHub Pro and programme-linked badges
Classification: Restricted or account-state dependent
Context: Some profile labels and programme indicators resemble achievements but reflect account plans, education programmes, security programmes, or organisational roles.
Current expectation: Do not combine these with the standard achievement trigger table unless GitHub explicitly categorises them as achievements.
Why historical accuracy matters
Outdated lists commonly mix together:
- current achievements;
- event badges;
- account-plan labels;
- programme membership indicators;
- contribution milestones;
- speculative or unreleased artwork.
This encyclopedia keeps those categories separate so readers are not directed toward impossible or misleading objectives.
Evidence needed for additions
A new historical entry should include at least one of the following:
- A dated GitHub announcement or documentation page.
- A verifiable profile example with contextual evidence.
- Archived documentation showing how the badge was awarded.
- Multiple independent observations that establish the timeframe and conditions.
Submit historical evidence · Return to the achievement index