Tool to fork repo and choose pull requests to merge

Kreijstal commented 2 years ago

Stale github repo Reviver

There are some repos where mantainers simply died, but helpful people have made multiple pull requests that would be useful to have in unison. It would be a shame to let all that work go to waste, but it's hard on the github interface to fork and merge various pull requests, so a tool would be nice, what I imagine is a web-tool like https://techgaun.github.io/active-forks/index.html the user selects the forks that wants to merge "in his own fork", and the output would be either:

a patch with all the patches together or
git commands that automatically take these external pull requests and merge them together in a branch Then the forker would simply paste the command, (possibly but not probably test) and push to github. This would be a nice way to start again active forks without losing the helpful pull requests :)

alternatively, and probably less aggressively, this would be useful to find out how two pull requests work together if they were merged.

Relevant Technology

git

Complexity and required time

Complexity

[ ] Beginner - This project requires no or little prior knowledge of the technolog(y|ies) specified to contribute to the project
[ ] Intermediate - The user should have some prior knowledge of the technolog(y|ies) to the point where they know how to use it, but not necessarily all the nooks and crannies of the technology
[x] Advanced - The project requires the user to have a good understanding of all components of the project to contribute

Required time (ETA)

[ ] Little work - A couple of days
[x] Medium work - A week or two
[ ] Much work - The project will take more than a couple of weeks and serious planning is required

KaKi87 commented 2 years ago

The idea itself is technically interesting but I don't think it's worth the effort :

those merges can easily be done using a real git client like SmartGit or the one included in JetBrains IDEs ;
merges may require human intervention, and probably knowledge of the software being forked ;
even if all forks merge successfully, any good coming out of it will be temporary as the project will still require further maintenance at some point.

Considering those facts, there would be no real benefit of creating an automated repository reviver, because the only way to revive a project is to actually maintain a fork, which is better done without such tool.

ketsapiwiq commented 2 years ago

Kreijstal commented 2 years ago

May be related: https://github.com/acsone/git-aggregator

that is pretty impressive

open-source-ideas / ideas