3 ms·
"Together with making it trivial to create commits and pull requests entirely in the browser" Isn't that a /good/ thing? The main hurdle I find when trying to
by pwaring 15y ago
"Together with making it trivial to create commits and pull requests entirely in the browser"
Isn't that a /good/ thing? The main hurdle I find when trying to fix problems in open source projects is working out how to submit my patch in a way which minimises the effort for the developer who has to review/merge it. As someone who has made and accepted pull requests, GitHub makes the process of accepting contributions about as easy as it can be.
With regards to poor-quality requests, that's something you have to accept as part of a project, just like poor-quality bug reports.
- streptomycin 15y agoIt's a good thing for most open source projects, which are starved for attention. It's probably not a good thing for an extremely popular project like Linux.
- pwaring 15y agoIf a project is very popular, something which makes it easier to handle pull requests is surely a good thing as well? That way developers spend more time coding and less time on review/merging (not that those aren't important tasks, but it seems sensible to streamline them if possible).
- mentat 15y agoI think the key feature would be something more along the lines of, "easier to handle pull requests that are required to be structured in specific ways" and "able to see exactly what a pull request will do".