Refined-github: Make it easy to delete forks

Created on 27 Oct 2017 · 14Comments · Source: sindresorhus/refined-github

You know the drill. You want to contribute, so you create a fork, do a simple change and create pull request. You repeat this few times and you have created tons of unused forks in your account which just make it harder to find your repos you actually care about. Can we do something about this? Make it easier to delete fork repos? Or maybe toggle to hide such repos?

bug help wanted

Source

ostrolucky

All 14 comments

We have added a link to delete your fork on a merged PR in #49 and fixed it in #321:

However, I think this has been broken again for some time now. I'll mark this issue as a bug.

@ostrolucky Are you willing to look into the code from the mentioned pull requests, find the cause why it's not working and submit a pull request? That would be awesome!

hkdobrev on 27 Oct 2017

I am seeing this even if i dont have access. Can we test the link to see if its leads to 404?

yakov116 on 30 Oct 2017

How can you not delete the fork if you can delete a branch (of a fork)? Where are you seeing this?

fregante on 31 Oct 2017

@bfred-it very simple if you have write access to a repo and that repo made a pull request to a fork

yakov116 on 31 Oct 2017

I think this can be verified by looking for the Settings tab in the repo. You can’t access that page, right?

PRs welcome

fregante on 31 Oct 2017

👍1

It would be lovely if this were available even before the PR is merged. GitHub PRs don't actually require the fork to exist in order to merge the PR, so I'd love to be able to insta-delete my fork after PRing. What do you think?

dwijnand on 11 Jan 2019

👍1

Bad idea, you don’t know if the PR is “good to go” and even if the maintainer is willing to make a change on the PR before merging… they can’t

fregante on 11 Jan 2019

Does deleting the repo indicate a PR is not "good to go"? It does make the PR immutable but that's an option for contributors even without deleting the repo.

dwijnand on 11 Jan 2019

It means that either the PR is good at first try or it has to be thrown out. It smells like “what I changed is good to go and I don’t care if it isn’t”

fregante on 11 Jan 2019

it has to be thrown out

No, it doesn't. Once you've re-forked, I haven't tested if you can or can't restore the branch from the web UI, but you can do it from the command line. Sure, if you can't from the web UI then it makes it a bit cumbersome, but maybe sometimes you want that choice.

dwijnand on 11 Jan 2019

It’s not a behavior I’d personally facilitate. It’s easier to just wait for the merge (you’ll be notified) and then delete it.

If you don’t want to have any forks on your repo, you can create an org and fork everything to that one. I use an org to archive my repos and anything I don’t want on my main profile, for example.

fregante on 12 Jan 2019

Yep, it's an alternative I've considered.

dwijnand on 12 Jan 2019

GitHub provides deleting a fork after merge/close out the box now: