In a nutshell, At SEF, we have something in store for everyone especially you are a student, expert, or a volunteer. After starting contributing to SEF I realised the importance of a quality PR and today I’m going to share those qualities with you.
First, let’s admit it: reviewing pull requests is really hard. As a reviewer, it’s your responsibility to make sure that the code is correct and of high quality before it gets merged into master. You are expected to do that by looking at a diff and list of files changed. You have to understand what the pull request is trying to achieve, what approach is being taken, what’s going on, and how all these files fit together — enough that you could potentially suggest an improvement. You may have to be on the lookout for typos or style problems. That’s a LOT of stuff a reviewer needs to do, especially in a large pull request!
I started to create understandable PRs since I started contributing to Sustainable Educational Foundation — SEF in late 2019. For those who don’t know about SEF please make sure to visit our site to know more details. In a nutshell, At SEF, we have something in store for everyone especially you are a student, expert, or a volunteer. After starting contributing to SEF I realised the importance of a quality PR and today I’m going to share those qualities with you.
Learn about branching, git create branch, git merge, git pull request, git switch branch and different This is the second part of a follow-along series on GitHub collaboration. In the first part, two coworkers, Sofi and Alec started working on a data cleaning project where they distributed tasks between each other, created and cloned repositories and made their first commits.branching workflows with git.
Learn how to submit your first pull request on GitHub in 100 seconds
How to submit your first pull request on GitHub in 100 seconds. Fork the repo below, then contribute a PR to receive a free hologram sticker in the mail http...
Learn about version controlling, git configuration, creating and cloning repository and committing. This is the first part of a follow-along series on GitHub collaboration. With this article, I aim to explain how two or more people can collaborate, version control and proofread their codes on GitHub for Data Science projects.
I recently worked with a team that was lacking a bit of documentation, so I took it upon myself to create some. In the process, I gained sympathy for authors of documentation. Documentation can often seem incomprehensible, and that’s in part because when you write documentation, you have to assume your audience has some baseline level of knowledge.