Tools and practices to hit the ground running
At 2DII we use a particular workflow – a set of tools and practices. This post is about what you should know to work effectively with us, or whoever uses the same workflow.
We collaborate on GitHub. Whatever your experience with GitHub, you may like these resources:
[GitHub] Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization’s data and projects with sophisticated security and administrative features. – About organizations
To join our GitHub organization you need to be invited by someone with special (“Owner”) privileges. Find that person by asking on the
#coding channel on 2DII’s Slack and share your GitHub username.
Most of our code on GitHub is written in R and from RStudio. Here is how to set things up:
Git is the heart of GitHub. We use it to track each meaningful change in our projects. You may use Git from the terminal or from a dedicated program (e.g. GitKraken); but you rarely need anything special because the most useful features of Git are available directly from RStudio.
We are working on multiple projects you may want to know about:
What else (or less) do you think a successful onboarding should have?
Caveat: In this video I violate the GitHub flow in that I submit a pull request not from a
feature branch (as I should) but from the