Removing a runner from a repository
Note: This procedure permanently removes the self-hosted runner. If you only want to temporarily stop a runner from being assigned jobs, you can either shut down the machine or stop the run application. The runner will remain assigned in an "Offline" state, and won't execute any jobs until you restart the runner using the run application.
A self-hosted runner is automatically removed from GitHub if it has not connected to GitHub Actions for more than 30 days.
To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine.
Alternatively, if you don't have access to the repository, organization, or enterprise on GitHub to remove a runner, but you would like to re-use the runner machine, then you can delete the .runner file inside the self-hosted runner application directory. This allows the runner to be registered without having to re-download the self-hosted runner application.
-
On GitHub, navigate to the main page of the repository.
-
Under your repository name, click Settings.
-
In the left sidebar, click Actions.
-
In the left sidebar, under "Actions", click Runners.
-
In the list of runners, click the runner you'd like to configure.
-
Click Remove.
-
You will see instructions for removing the self-hosted runner. Complete either of the following steps to remove the runner, depending on whether it is still accessible:
-
If you have access to the runner machine: Follow the on-screen instructions for your machine's operating system to run the removal command. The instructions include the required URL and an automatically-generated, time-limited token.
The removal command does the following tasks:
- Removes the runner from GitHub.
- Removes any self-hosted runner application configuration files on the machine.
- Removes any services configured if not running in interactive mode.
-
If you don't have access to the machine: Click Force remove this runner to force GitHub to remove the runner.
-
Removing a runner from an organization
Note: This procedure permanently removes the self-hosted runner. If you only want to temporarily stop a runner from being assigned jobs, you can either shut down the machine or stop the run application. The runner will remain assigned in an "Offline" state, and won't execute any jobs until you restart the runner using the run application.
A self-hosted runner is automatically removed from GitHub if it has not connected to GitHub Actions for more than 30 days.
To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine.
Alternatively, if you don't have access to the repository, organization, or enterprise on GitHub to remove a runner, but you would like to re-use the runner machine, then you can delete the .runner file inside the self-hosted runner application directory. This allows the runner to be registered without having to re-download the self-hosted runner application.
-
On GitHub, navigate to the main page of the organization.
-
Under your organization name, click Settings.
-
In the left sidebar, click Actions.
-
In the left sidebar, under "Actions", click Runners.
-
In the list of runners, click the runner you'd like to configure.
-
Click Remove.
-
You will see instructions for removing the self-hosted runner. Complete either of the following steps to remove the runner, depending on whether it is still accessible:
-
If you have access to the runner machine: Follow the on-screen instructions for your machine's operating system to run the removal command. The instructions include the required URL and an automatically-generated, time-limited token.
The removal command does the following tasks:
- Removes the runner from GitHub.
- Removes any self-hosted runner application configuration files on the machine.
- Removes any services configured if not running in interactive mode.
-
If you don't have access to the machine: Click Force remove this runner to force GitHub to remove the runner.
-
Removing a runner from an enterprise
Note: This procedure permanently removes the self-hosted runner. If you only want to temporarily stop a runner from being assigned jobs, you can either shut down the machine or stop the run application. The runner will remain assigned in an "Offline" state, and won't execute any jobs until you restart the runner using the run application.
A self-hosted runner is automatically removed from GitHub if it has not connected to GitHub Actions for more than 30 days.
To remove a self-hosted runner from an enterprise account, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine.
-
In the top-right corner of GitHub, click your profile photo, then click Your enterprises.
-
In the list of enterprises, click the enterprise you want to view.
-
In the enterprise sidebar, click Policies.
-
Under " Policies", click Actions.
-
Click the Runners tab.
-
In the list of runners, click the runner you'd like to configure.
-
Click Remove.
-
You will see instructions for removing the self-hosted runner. Complete either of the following steps to remove the runner, depending on whether it is still accessible:
-
If you have access to the runner machine: Follow the on-screen instructions for your machine's operating system to run the removal command. The instructions include the required URL and an automatically-generated, time-limited token.
The removal command does the following tasks:
- Removes the runner from GitHub.
- Removes any self-hosted runner application configuration files on the machine.
- Removes any services configured if not running in interactive mode.
-
If you don't have access to the machine: Click Force remove this runner to force GitHub to remove the runner.
-