# A Repository Graveyard

DevFeed: [A Repository Graveyard](<https://devfeed.tech/articles/a-repository-graveyard-37834.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/repositories-graveyard/>)

Author: Carlos Alexandro Becker

Published: 2017-09-04T00:00:00Z

Content type: article

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [Code](<https://devfeed.tech/topics/code.md>), [opensource](<https://devfeed.tech/topics/opensource.md>)

Tags: [deprecated](<https://devfeed.tech/tags/deprecated.md>), [github](<https://devfeed.tech/tags/github.md>), [opensource](<https://devfeed.tech/tags/opensource.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [repository](<https://devfeed.tech/tags/repository.md>), [webhook](<https://devfeed.tech/tags/webhook.md>)

## AI overview

A developer describes cleaning up a long-used GitHub profile by moving abandoned repositories to a graveyard organization, deleting empty scaffolds, and updating a fork-cleaner utility. The process reduced the account from roughly 270 repositories to 54 and led to a webhook that responds to new issues and pull requests on unmaintained repositories.

## Source excerpt

This past weekend I decided I need to clean up my GitHub profile. In this post I'll write about why I cleaned everything up and also how I did, as well as some initial results.