Repo Settings

Overview

You can manage the settings for a specific repository by navigating to that repository and then clicking on the Settings tab.

Repository

To manage your general settings for your repository, click into the Repository tab.

Managing Basic Settings

The Basic Settings section is home to general repository settings.

Most often, you will navigate here to change the name and description of your repository. You can also set the repository as a template by checking the Template option. To learn more about how and when to use templates, check out the Creating Templates section.

Managing Advanced Settings

Additional settings and features live in the Advanced Settings section.

By default, the Wiki option will be active. Unchecking this option will disable the Wiki feature for your repository and remove it from the nav bar.

If you prefer to use an external Wiki, choose the Use External Wiki option and enter a valid URL into the field.

The Issues option will also be automatically checked. Turning this option off will disable the Issues feature for your repository and remove it from the nav bar.

If you prefer to use an external issue tracker, choose the _Use External Issue Tracke_r option and enter a valid URL into the field.

Transferring, Deleting, and Archiving Repositories

Within the Danger Zone section you can perform some high level and potentially risky operations:

• Transferring ownership - This enables you to transfer the repository to another Organization within Copia. You would have to have Administrator or Owner access to this separate Organization.

• Deleting Wiki Data - This allows you to delete the data from the repository's Wiki. Because deleting a Wiki is a permanent change, you would want to copy the Wiki over to another location before proceeding.

• Deleting the Repository - This irreversibly removes the repository and its data from your Organization.

• Archiving the Repository - This reversible feature prevents superfluous edits to a project that has reached completion. You would still have Read-Only access to the archived repository.

Collaborators

The core of any collaborative flow starts with granting a user access to your repository.

To manage the collaborators within your repository, click into the Collaborators tab.

Adding and Removing Collaborators

Within the Collaborators section, enter the email address of each collaborator you wish to add. Press the Add Collaborator button to add them to the repository.

If the invitee already has a Copia account, they will automatically be added to your repository. Otherwise, they will receive an invitation email to create an a Copia account and then join your repository.

The collaborator's account will be displayed once they're successfully added. You can remove the collaborator from the repository by clicking the red Remove button.

Managing Privileges for Collaborators

Once a user has been added to a repository, the next step is to manage their access rights. There are three types of access rights in Copia:

• Read - These users can read files but cannot modify them.

• Write - These users can read and write files but cannot modify repository settings.

• Administrator - These users can add and remove collaborators. They can also perform potentially destructive actions like deleting a repository and transferring ownership.

To assign a privilege onto a collaborator, click the Privilege Selector and choose an option from the dropdown. Your selection will automatically be saved.

Managing Team-Level Access

If you want to grant access to a group of individuals (ex., you might want to provide read access to a group of contractors), you can set a Team as a collaborator for a repository.

In the Organization Management screen, you will need to assign Members to your Team as per the steps outlined in the Teams section. There, you will assign specific repositories to Teams you've created.

If a Team has been given access to your repository, it will be listed in the Teams section.

You can add a new Team as a collaborator by entering the Team name in the Search Team field and clicking the Add Team button.

Branches

Branches allow each developer on your team to have a copy of the source code to work with.

To manage your branching settings, click into the Branches tab.

Setting a Default Branch

By default, new pull requests and code commits will use main. You can set a different default branch to better suit your specific workflow.

To set a new default branch, select the Branch Selector within the Default Branch section and choose a new branch. Click the Update Settings button to save your changes.

Setting Branch Protections

Branch protection includes rules and configurations an Owner or Administrator of a repository can set to control who can edit the specific branch.

To learn more about how and when to set branch protections, review the Branch Protections section.

Webhooks

Webhooks are automated messages sent from the Copia server when something happens in your repository. These messages are posted via HTTP to a specific URL of an App that is waiting to receive the message.

To learn more about how to create webhooks and view the available integrations, see the Integrations section.