Archiving repositories
Just because a repository isn’t actively developed anymore and you don’t want to accept additional contributions doesn’t mean you want to delete it. Now archive repositories on GitHub to make…

Just because a repository isn’t actively developed anymore and you don’t want to accept additional contributions doesn’t mean you want to delete it. Now archive repositories on GitHub to make them read-only.
Archiving a repository makes it read-only to everyone (including repository owners). This includes editing the repository, issues, pull requests, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions and comments. No one can create new issues, pull requests, or comments on an archived repository, but you can still fork archived repositories—allowing development to continue elsewhere for archived open source projects.
To archive a repository, go to your Repository Settings Page and click Archive this repository.
Before archiving your repository, make sure you’ve changed its settings and consider closing all open issues and pull requests. You should also update your README and description to make it clear to visitors that it’s no longer possible to contribute.
If you change your mind and want to unarchive your repository, click Unarchive this repository in the same place. Please note that most archived repository settings are hidden and you’ll have to unarchive the repository to change them.
To learn more, check out the documentation on archiving repositories. Happy archiving!
Written by
Related posts

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.