How to remove a Github Environment

Question

My question is about cleaning up the "Environments" tab on a Github repository.

I previously deployed via Heroku, using automatic deployment from two separate Github branches (one for staging, one for production).

This created a tab "Environments" on the repository, in which both Heroku environments were shown - exactly as intended.

Once I started to dive into Heroku pipelines, I have now configured the app to be promoted to production from staging, so the production environment no longer auto-deploys from a branch.

The Environments tab on my Github repo has no way to remove the environment that I no longer use. I can't seem to find any place on Github or Heroku to make Github "forget" this deployment environment.

I hope my question is clear enough; if I can elaborate on anything, please let me know.

Answer 1

I made a little webpage/script too, to automate the process (I don't have Python installed, and I didn't see that someone else had already made a script), and this is online and putting your info will do the process automatically.

Stackblitz - Github Deployments deleter

Edit 18/07/2020: I copied the script from Stackblitz to a local snippet code in here too, just in case Stackblitz disappears:

// RECOMMENDED: Disconnect HEROKU from Github before doing this (though not strictly necessary, I think).
//See https://stackoverflow.com/a/61272173/6569950 for more info.

// PARAMETERS
const TOKEN = ""; // MUST BE `repo_deployments` authorized
const REPO = "your-repo"; // e.g. "monorepo"
const USER_OR_ORG = "your-name"; // e.g. "your-name"

// GLOBAL VARS
const URL = `https://api.github.com/repos/${USER_OR_ORG}/${REPO}/deployments`;
const AUTH_HEADER = `token ${TOKEN}`;

// UTILITY FUNCTIONS
const getAllDeployments = () =>
  fetch(`${URL}`, {
    headers: {
      authorization: AUTH_HEADER
    }
  }).then(val => val.json());

const makeDeploymentInactive = id =>
  fetch(`${URL}/${id}/statuses`, {
    method: "POST",
    body: JSON.stringify({
      state: "inactive"
    }),
    headers: {
      "Content-Type": "application/json",
      Accept: "application/vnd.github.ant-man-preview+json",
      authorization: AUTH_HEADER
    }
  }).then(() => id);

const deleteDeployment = id =>
  fetch(`${URL}/${id}`, {
    method: "DELETE",
    headers: {
      authorization: AUTH_HEADER
    }
  }).then(() => id);

// MAIN
getAllDeployments()
  .catch(console.error)
  .then(res => {
    console.log(`${res.length} deployments found`);
    return res;
  })
  .then(val => val.map(({
    id
  }) => id))
  .then(ids => Promise.all(ids.map(id => makeDeploymentInactive(id))))
  .then(res => {
    console.log(`${res.length} deployments marked as "inactive"`);
    return res;
  })
  .then(ids => Promise.all(ids.map(id => deleteDeployment(id))))
  .then(res => {
    console.log(`${res.length} deployments deleted`);
    return res;
  })
  .then(finalResult => {
    const appDiv = document.getElementById("app");
    appDiv.innerHTML = `
<h1>CLEANUP RESULT</h1>
<br>
Removed Deployments: ${finalResult.length}
<br>
<br>Ids:<br>
${JSON.stringify(finalResult)}
<br><br><br><br><br><br>
  <p>(Open up the console)</p>
`;
  });

h1,
h2 {
  font-family: Lato;
}

<div id="app">
  <h1>Github Deployment's Cleaner</h1>
  <p> You need to put the parameters in!</p>
</div>

Answer 2

I've built an online tool to help out removing deployments

I ran into the same problem and found @spersico's code very handy, but needed a bit more tooling/feedback. I iterated on @spersico code to add a bit of frontend. Same as @spersico's version, all calls are made client side (and are visible in your console/network logs).

Project is opensource on Github and has a hosted version on Netlify which can be used instantly: https://github-deployment-cleaner.netlify.app/

Answer 3

I don't know if this was posted already but I definitely didn't want do delete my 40+ deployments manually so I created following script, feel free to use it too :)

#!/bin/bash

REPO=<your GH name>/<your project name>
TOKEN=<your personal access token>

# https://starkandwayne.com/blog/bash-for-loop-over-json-array-using-jq/
for deployment in $(curl https://api.github.com/repos/$REPO/deployments | jq -r '.[] | @base64'); do
    DEPLOYMENT_ID=$(echo "$deployment" | base64 --decode | jq -r '.id')
    echo "$DEPLOYMENT_ID"
    curl "https://api.github.com/repos/$REPO/deployments/$DEPLOYMENT_ID/statuses" \
        -X POST \
        -d '{"state":"inactive"}' \
        -H 'accept: application/vnd.github.ant-man-preview+json' \
        -H "authorization: token $TOKEN"
done
for deployment in $(curl https://api.github.com/repos/$REPO/deployments | jq -r '.[] | @base64'); do
    DEPLOYMENT_ID=$(echo "$deployment" | base64 --decode | jq -r '.id')
    curl "https://api.github.com/repos/$REPO/deployments/$DEPLOYMENT_ID" \
        -X DELETE \
        -H "authorization: token $TOKEN"
done

Answer 4

I've just used this Python script: 5 minutes and I removed my unwanted environment:

https://github.com/VishalRamesh50/Github-Environment-Cleaner

There is a discussion in GitHub Community: https://github.community/t/how-to-remove-the-environment-tab/10584/10?u=aerendir

Please, vote up the feature.

Answer 5

I Expect Your already got the answer for your question This answer is for those who wan't to Remove The Environments Tab from There GitHib Repo

As I Understand

• If You Want to Remove the Environments Tab Shown on The Right Side of The Screen

• If You Want to Remove Specific Environments

Remove Environments Tab

To Remove Entire Tab

1. On Your Repo Page Click on Settings Button
   
2. Uncheck the Mark on Environments
   

It Will Remove The Environments Tab from the Right Side

Remove Specific Environments

For Removing Specific Environment

1. Click on Settings
   
2. Click On Environments
   
3. Here You Can Remove a Specific Environment
   

---

Reply from GitHub for Removing of Environments from Private Repo

Hi Deekshith,

Thanks for writing in!

As it turns out, the Environments feature is an enterprise-only feature for private repositories, however, they still get created as a side effect of Deployments in private repositories.

https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment

This means that though you'd be able to create Deployments in a private repository, you won't be able to manage (e.g delete, add rules e.t.c) the deployment Environments. I'm afraid this is currently the expected behaviour. Our engineers are still discussing how best to help users who'd want to delete environments in non-enterprise private repositories, such as in your case. We’ll be sure to update you as soon as there’s any news to share.

Sorry that we could not be of more help with this -- please let us know if you have any questions at all!

Regards,
Peter
GitHub Support

Answer 6

This will not answer the OP question, I thought it would at first, but it didn't behave as I had expected. Therefore, I'm adding this answer as a community wiki.

GitHub seems to have two notions of "Environments", the one the OP means are "public environments", but GitHub also seems to have some kind of "private environments".

I'm adding my experience as an answer below because it is really confusing.

---

You can access "private environments" through "Settings > Environments". (E.g: https://github.com/UnlyEd/next-right-now/settings/environments)

You can then delete each environment. It'll prompt a confirm dialog. Upon confirm, the environment will be destroyed.

I deleted the "staging" and "production" environments.

But the public environments still continue to exist, alongside all their deployments. (and this is not what the OP wants)

Public environments still contains "staging" and "production".

Answer 7

Unfortunately, it seems that the 'Deployments' dashboard is currently in beta, which means that they may not have a feature yet.

Read here.

Answer 8

Using GitHub CLI:

org=':org:'
repo=':repo:'
env=':env:'

gh api "repos/${org}/${repo}/deployments?environment=${env}" \
  | jq -r ".[].id" \
  | xargs -n 1 -I % sh -c "
  gh api -X POST -F state=inactive repos/${org}/${repo}/deployments/%/statuses
  gh api -X DELETE repos/${org}/${repo}/deployments/%
"

Answer 9

You can remove the environment from a repository if its public. But in case of private repositories, either you have to make it public or use the github API. Both works, but here is my approach for deleting the environments.

I created an npm package (here) for the same. Just get the github access token, with repo_deployments scope enabled.

Now run npx delete-github-environment and select the environment that you want to delete. If everything went right, your environment will be deleted.

PS: Here's my github repo - (github), feel free to contribute to the code.

Answer 10

There doesn't seem to be UI for it, but you can do it using the GitHub API.

You should probably disconnect GitHub and Heroku before doing this.

First, go to your GitHub account settings, then developer settings, then personal access tokens. Create a new token that has repo_deployments allowed. After it's generated, save the hexadecimal token, you'll need it for the upcoming API requests.

For these examples I'll assume that your username is $aaaa and your repo name is $bbbb and your access token is $tttt. Replace these with your actual username and repo name and access token. Or just use shell variables to store the actual values which will let you paste the code blocks directly.

First, list all the deployments on your repo:

curl https://api.github.com/repos/$aaaa/$bbbb/deployments

Each deployment has an id integer. Note it, and replace $iiii in the upcoming code blocks with that ID. Or create another shell variable for it.

Now you have to create an "inactive" status for that deployment:

curl https://api.github.com/repos/$aaaa/$bbbb/deployments/$iiii/statuses -X POST -d '{"state":"inactive"}' -H 'accept: application/vnd.github.ant-man-preview+json' -H "authorization: token $tttt"

And now you can delete the deployment forever:

curl https://api.github.com/repos/$aaaa/$bbbb/deployments/$iiii -X DELETE -H "authorization: token $tttt"

If you have multiple deployments, send the first request to see all the deployments that remain, and then you can delete those too if you want.

After you delete all the deployments, the environments button on the GitHub repo will disappear.

Information sourced from the GitHub deployments documentation and the GitHub oauth documentation. This worked for me.

Answer 11

To remove a Github Environment go to Settings -> Environments -> and click the trashcan icon next to the Environment you want to delete (see picture below).

More can be read about it from the Github official documentation: Deleting an Environment

Answer 12

After a bit of trial and error, I came up with this.

1. Install octokit: npm i @octokit/core
2. copy the code below in a filename.js
3. in the terminal, type node filename.js

const { Octokit } = require("@octokit/core");
    
const owner = "OWNER";
const repo = "REPO";
const token = "TOKEN";
    
(async () => {
    const octokit = new Octokit({
        auth: token
    })

    //get all deployments to get id
    let deployments = await octokit.request(`GET /repos/${owner}/${repo}/deployments`, {
        owner: 'OWNER',
        repo: 'REPO',
        headers: {
            'X-GitHub-Api-Version': '2022-11-28'
        }
    })

    //iterate through them
    deployments.data.forEach(async ({ id }) => {
        //set deployment as inactive (relevant if it is the last one)
        await octokit.request(`POST /repos/${owner}/${repo}/deployments/${id}/statuses`, {
            environment: 'production',
            state: 'inactive',
            log_url: 'https://example.com/deployment/42/output',
            description: 'Deployment finished successfully.',
            headers: {
                'X-GitHub-Api-Version': '2022-11-28'
            }
        })

        //delete deployment
        await octokit.request(`DELETE /repos/${owner}/${repo}/deployments/${id}`, {
            headers: {
                'X-GitHub-Api-Version': '2022-11-28'
            }
        })
    })
})()

I've used it to get rid of Vercel deployments, but it should work for any kind of deployment.

Feedback is appreciated!

Answer 13

For future references this will be helpful. First click the repository which you want to work on.Then click on deployments.

Inside the new page click manage environments

Still on the same page click on the trash bin icon

Afterwards you will be prompted to enter your password and after entering your password.After entering your password you will see this pop up

Answer 14

Based on Cadence's answer, I built the following bash script. Just set the appropriate parameters and let it run.

The token requires repo_deployment OAuth scope.

env=asd
token=asd
repo=asd
user=asd

for id in $(curl -u $user:$token https://api.github.com/repos/$user/$repo/deployments\?environment\=$env | jq ".[].id"); do
    curl -X POST -u $user:$token -d '{"state":"inactive"}' -H 'accept: application/vnd.github.ant-man-preview+json' https://api.github.com/repos/$user/$repo/deployments/$id/statuses
    curl -X DELETE -u $user:$token https://api.github.com/repos/$user/$repo/deployments/$id
done

Answer 15

I've made an interactive python script which can delete specific environments by name (which was my issue) or all of your deployments. Check it out and let me know if it works for you: https://github.com/VishalRamesh50/Github-Environment-Cleaner.

This will also actually delete all of your deployments even if you have more than 30 unlike the other scripts here because it goes through the paginated response data from Github's API and doesn't just use the first page.