6 ms·
For most folks who already have an account, it's just a matter of clicking the "edit" icon on the top right of a file, making the change, then saving it. GitHub
by jvehent 8y ago
For most folks who already have an account, it's just a matter of clicking the "edit" icon on the top right of a file, making the change, then saving it. GitHub does everything else under the hood, and creates a fork and pull request programmatically.
We can debate the value of centralized web interfaces to vcs systems all day long, but the fact that they immensely simplify contributing to open source software cannot be understated.
- u801e 8y ago> For most folks who already have an account, it's just a matter of clicking the "edit" icon on the top right of a file, making the change, then saving it. From what I've read, it could lead to badly formatted files and commit messages (since the online editor may not handle wrapping or spacing correctly). Plus, how does one test a change they make if they just made it in an online editor? If their contribution has syntax errors because they didn't even run the code, then is it a worthwhile contribution?
- jvehent 8y agoModern projects don't rely on local linting and testing, but instead leverage continuous integration platforms like travisci or circleci for verification.
- u801e 8y agoDoes that apply to forks of the project? Or is the only way to test the project is to open the PR and check the build status on the upstream? Personally, I would like to know that my code is in a working state before I actually submit it to the maintainer for review.