How to Remove a Contributor from a GitHub Repository

Removing a contributor from a GitHub repository is straightforward when you have the required permissions, but it is important to understand the difference between removing direct access and removing every possible route to the repository. A person may have access directly, through an organization team, or through broader organization permissions.

In this guide, we’ll cover how to remove a contributor from a GitHub repo, revoke collaborator access, remove an outside collaborator, handle team-based access, and check what happens to forks and local copies.

What does removing a GitHub contributor actually do?

On GitHub, repository access can be granted to an individual, a team, or through organization-level permissions. Removing someone as a direct collaborator removes that direct repository access, but it does not necessarily eliminate access granted through another route.

GitHub says people with admin access to a repository can manage teams and people with access, change their roles, or remove access. citeturn0search8

How to remove a contributor from a personal GitHub repository

If the repository belongs to your personal GitHub account, you can remove a collaborator from the repository settings.

1. Open the GitHub repository.
2. Click Settings. If Settings is hidden, open the repository dropdown and select Settings.
3. In the sidebar, under Access, select Collaborators & teams.
4. Find the contributor you want to remove.
5. Click Remove next to their name.

GitHub documents this as the standard process for removing collaborator permissions from a personal repository. citeturn0search2

How to remove a contributor from an organization repository

For an organization-owned repository, repository administrators can manage individual access from the repository’s access settings.

1. Open the repository on GitHub.
2. Go to Settings.
3. Open Collaborators & teams under the Access section.
4. Find the person under Manage access.
5. Click Remove.

GitHub’s access-management documentation confirms that repository admins can view people and teams with access and remove a person or team from the repository. citeturn0search8

What if the contributor is an organization team member?

This is where simply removing a person as a direct collaborator can be misleading. If their access comes from a team, you need to review the team’s repository permissions.

GitHub allows repository administrators to manage team access. If a team’s access is inherited from a parent team, changing the parent team’s repository access may be necessary. citeturn0search7

Before assuming the person has been completely removed, check the repository’s access overview for the source of their permissions. GitHub can show a Mixed roles warning when a person has conflicting access grants. citeturn0search8

How to remove an outside collaborator

An outside collaborator is someone who has access to an organization’s repositories without being an organization member.

Organization owners and repository administrators can remove an outside collaborator. GitHub also provides an organization-level option for removing an outside collaborator from all repositories where they have access. citeturn0search3turn0search4

If you only want to remove access to one repository, use the repository’s access-management settings rather than removing the person from every repository.

What happens to the contributor’s fork?

This is one of the most important things to understand before removing someone.

For a private repository, GitHub says that removing a collaborator causes their private fork to be deleted. However, their local clone of the repository is not automatically deleted. citeturn0search1turn0search4

That means removing GitHub access is not the same as remotely deleting every copy of your code. If the repository contains confidential information or intellectual property, you should consider what the person may already have downloaded or copied.

Does removing a contributor delete their commits?

No. Removing someone’s repository access does not mean their existing Git history simply disappears. Commits already present in the repository remain part of its history unless you deliberately rewrite history or otherwise change the repository.

If your concern is that a secret, password, API key or other sensitive information was committed, removing the contributor is not enough. Treat the credential as exposed and rotate or revoke it, then follow GitHub’s guidance for removing sensitive data from repository history.

What should you check after removing a contributor?

For a clean offboarding process, do more than click Remove.

• Review the repository’s access list.
• Check whether the person still has access through an organization team.
• Review organization-level permissions where relevant.
• Remove unnecessary access to related private repositories.
• Rotate credentials or secrets the person may have had access to.
• Review deploy keys, personal access tokens, GitHub Apps and other integrations if applicable.
• Check active branches, pull requests and automation owned by the departing contributor.

GitHub’s repository access overview is specifically intended to help administrators audit access and offboard contractors or employees. citeturn0search8

Can you remove a contributor using the GitHub API?

Yes. GitHub provides a REST API endpoint for removing a repository collaborator. The authenticated user must be a repository administrator or be removing themselves. The endpoint returns HTTP 204 when the collaborator is removed successfully. citeturn0search9

The API route is useful for automated offboarding and administration, but the same access caveat applies: a person may still have access through organization-level permissions or another team.

Related GitHub contributor removal searches

If you are looking for how to remove a contributor from GitHub repo, related searches include how to remove a collaborator from GitHub, remove GitHub collaborator, revoke GitHub repository access, remove contributor from GitHub repository, remove someone from GitHub repo, GitHub remove user access, remove outside collaborator GitHub, and GitHub repository access management.

Frequently asked questions

Can I remove a contributor if I am not a repository admin?

Generally, you need the appropriate administrative access to manage another person’s repository access. GitHub’s documentation states that people with admin access can manage teams and people with access to a repository. citeturn0search8

Does removing a contributor delete their local copy?

No. Removing GitHub access cannot remotely delete a local clone that the person already has.

Will a contributor’s private fork be deleted?

For a private repository, GitHub says the person’s private fork is deleted when their repository access is removed. Their local clone remains. citeturn0search1

What if the contributor still has access after I remove them?

Check whether they receive access through an organization team, organization-wide permissions, or another access grant. GitHub’s repository access page can help identify conflicting or mixed roles. citeturn0search8

Final takeaway

Removing a contributor from a GitHub repository is more than removing a username from a list. The safest approach is to revoke direct access, check team and organization permissions, review credentials, and confirm that the person’s remaining access is appropriate.

For routine contributor offboarding, GitHub’s Collaborators & teams access page is usually the best place to start.