What is the primary effect of archiving a GitHub repository for ongoing development work?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Archive = read-only museum mode for inactive code. Unarchive to work again. It doesn't delete tags or teleport you to GHES.
Full explanation below image
Full Explanation
Archiving a repository freezes it in a read-only state appropriate for retired or dormant projects. Users can still view and clone content depending on visibility, but collaborative mutations such as pushes, creating issues, or merging pull requests are not available until the repository is unarchived by someone with sufficient rights. Archiving does not schedule deletion of releases and tags, nor does it migrate hosting to GitHub Enterprise Server. Administrators should use archive instead of deletion when retention, audit, or compliance needs remain, document ownership of archived assets, and apply lifecycle policies so archives do not accumulate secrets that never get rotated.