Skip to content

Update archiving-public-repositories.md #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jeffrey-Luszcz merged 1 commit into from
Apr 1, 2025
Merged

Update archiving-public-repositories.md #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/archiving-public-repositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,5 @@ In order to archive a github organization repository:
3. Let it sit until you receive confirmation from a maintainer or an adequate length of time has passed.

4. Close all open issues and pull requests and archive the repository from the repository settings.

Note: It is important to typically choose to **Archive** unmaintained repositories instead of deleting them. When you delete a public repository, the oldest, [active public fork is chosen to be the new upstream repository](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility). All other repositories are forked off of this new upstream and subsequent pull requests go to this new upstream repository. This may have security and reputational risks to your organization. If you must delete a repository, work with your OSPO or similar team to understand the implications of this process.