Managing repository settings

You can choose who can view your repository.

To help other people find and contribute to your project, you can add topics to your repository related to your project's intended purpose, subject area, affinity groups, or other important qualities.

To keep certain files from displaying in diffs by default, or counting toward the repository language, you can mark them with the linguist-generated attribute in a .gitattributes file.

You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository.

You can customize the image displayed on social media platforms when someone links to your repository.

You can view information about deployments for your entire repository or a specific pull request.

You can allow or prevent the forking of a specific private or internal repository owned by an organization.

Repository administrators can turn off project boards for a repository if you or your team manages work differently.

You may wish to turn issues off for your repository if you do not accept contributions or bug reports.

As a repository administrator, you can enable or disable anonymous Git read access for public repositories that meet certain requirements.

You can add autolinks to external resources like JIRA issues and Zendesk tickets to help streamline your workflow.

You can rename a repository if you're either an organization owner or have admin permissions for the repository.

You can transfer repositories to other users or organization accounts.

You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.