3 ms·
This is pointless. If your fork is no longer maintained you should say so and not accept pull requests. Let the other person maintain their own fork and accept
by tantalor 14y ago
This is pointless. If your fork is no longer maintained you should say so and not accept pull requests. Let the other person maintain their own fork and accept pull requests to their fork.
- Smudge 14y agoI wish Github made it easier to capture the fact that forks often diverge and become their own distinct (but related) projects. Right now you have to email support and ask them to detach the fork, which detaches everything from the previous graph of forks & commits. (The graph is important -- Often when I find a useful but less-than-maintained project, I search the graph to find a fork that is better maintained.)
- bhaak 14y agoIn a first step you can have a descriptive branch name for your default branch and if you feel you need to go further you can rename your repository. Isn't this enough? For really popular forks you can often see that in the members tab many sub forks have forked off them. This is a good hint for a project that has left the original repository behind.
- mkolodny 14y agoThe cool part of the hack isn't that you do this for projects you're no longer maintaining - it's that you give others commit privilege for projects you _are_ maintaining. OP's point was this empowers others by giving them ownership of the project, and leads to better work.