Danger Zone

Danger Zone

The Danger Zone contains high-impact settings that can change access, ownership, or availability of your repository.
These actions can affect collaborators, integrations, and historical data, so proceed with caution.

Visibility

Controls whether the repository is public or private.

See Repository Privacy

Why this matters:
Visibility changes affect how widely your work is accessible—public repos support open collaboration, while private repos protect sensitive or proprietary content. Adjusting this setting can also impact integrations or builds that rely on public access.

To change your privacy click the "Make Public" or "Make Private" button.

See Repository Privacy

Transfer Ownership

Moves the repository to another user or organization where you have admin permissions.

Why this matters:
Ownership determines who controls repository settings, billing, integrations, and access management.
Transfers are commonly used when:

• A project moves to a different team
• An organization acquires responsibility for a repository
• Personal projects graduate into shared or organizational use
• Someone accidentally creates a personal repository and needs to change the owner to an Organization.

After transfer, the new owner becomes responsible for permissions and administration.

Step-by-step guide to Transfer Repository Ownership to Another User or Organization

PDF Guide

1. Your Organization Team must have "Create repositories" checked. If your "Accept" or "Reject" buttons are disabled, contact your Organization lead and direct them to https://learn.allspice.io/docs/how-to-configure-teams to set "Create repositories to checked
   
2. You can see here that the Organization AllSpice-Demos has a Team called Contributors, and has Create repositories access.
   
3. Click on repository Settings to begin Transferring ownership of the repo. You will then scroll all the way down to the Danger Zone
   
4. Scroll down to the 'Danger Zone' and select 'Transfer Ownership' to begin transferring the repository.
   
5. Enter the repository name as confirmation before transferring ownership.
   
6. Type the username or organization for the new repository owner.
   
7. Click 'Perform Transfer' to finalize transferring the repository to the new owner.
   
8. Click on "Accept Transfer" to finish changing owners
   
9. If your Team was configured correctly, you should see a confirmation. If not, let's troubleshoot
   
10. If "Accept Transfer" and "Reject Transfer" are disabled, you need an Organization Owner to change your Team Configurate to set "Create repositories" to checked.https://learn.allspice.io/docs/how-to-configure-teams

Delete This Repository

Permanently deletes the repository and its contents.

• All files, issues, pull requests, design reviews, and settings are removed.
• This action cannot be undone.

Why this matters:
Deletion is irreversible. Only use this option when a repository is no longer needed or has been migrated elsewhere. Consider archiving as a safer alternative if you may need the data later.

Archive This Repository

Archives the repository, making it fully read-only.

Effects of archiving:

• Hidden from dashboards and activity feeds
• No new commits, issues, pull requests, or design reviews can be created
• Existing content remains accessible for reference
• Can be unarchived at any time

Why this matters:
Archiving preserves the repository for historical or regulatory purposes while preventing accidental changes. This is ideal for completed projects, deprecated hardware revisions, or repositories kept solely for documentation or traceability.