We all have them, repositories that gather digital dust. They haven't been updated in years, with no plans to ever touch them again. Repos that we no longer look at, and get no love. GitHub doesn't limit the number of repositories so there is no incentive to tidy them up.
You have probably always wanted a way to say "Bye Felicia" to your repo and it would automatically be deleted. Well, you are in luck because that is what I built. Say hello to the Bye Felicia GitHub Action.
For those unfamiliar with the term here is a link to learn more.
My Workflow
"Bye Felicia" is the newest GitHub Action sure to be integrated into the actions toolkit package to make it easier to delete your repositories.
Submission Category:
- Wacky Wildcards
Yaml File
Just add this action to your repos and whenever you don't want them anymore just say "Bye Felicia" in an issue comment and it will be deleted and 404.
Here is an example being triggered by an issue comment:
name: π Felicia
on:
issue_comment:
types: [ created ]
jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Run bye-felicia action
uses: tonydiaz/bye-felicia-github-action@main
with:
github-secret: ${{ secrets.REPO_ACCESS_TOKEN }}
github-repository: ${{ github.repository }}
Link to Code
π Felicia GitHub Action
GitHub action that will delete your repository.
We all have them, repositories that gather dust. They been updated in years, with no plans to ever touch them again. Repos that no one looks at, potentially using versions of software that are now depricated. Let's face it we don't do a good job cleaning up our old repositories. Cleanup of repos is where this Github Action shines.
By adding this action all you will ever need to do is say Bye Felicia!
in a issue comment and your repo is no more.
Required:
REPO_ACCESS_TOKEN - You will need to create a personal access token to access have the ability to delete a repository. Add that token as a secret in your repo.
Example usage
uses: tonydiaz/bye-felicia-github-action@main
with:
github-secret: ${{ secrets.REPO_ACCESS_TOKEN }}
Top comments (1)
YES! THIS IS WHAT I NEED! Thank you.