Back to Course
Using Git and GitHub with R
0% Complete
0/0 Steps
-
Welcome, Logistics, Course Materials, and Additional Resources
-
Introduction to Git and GitHubWhat is Git? What is GitHub?
-
Why Should You Learn to Use Git and GitHub?
-
Update Everything
-
GitInstall Git
-
Configure Git
-
Create a Local Git Repository
-
Commits
-
Commit History
-
GitHubGitHub Repositories
-
Connect RStudio and GitHub
-
Push an RStudio Project to a GitHub Repository
-
Pull a GitHub Repository to an RStudio Project
-
Keep RStudio and GitHub in Sync
-
Collaborating with Git and GitHubWhy Use GitHub vs Dropbox, Google Drive, Box, etc?
-
Dealing with Common Problems: Can't Pull Code from GitHub
-
Dealing with Common Problems: Merge Conflicts
-
Dealing with Common Problems: Can't Push Code to GitHub
-
Let's Keep Bad Things from Happening in the First Place
-
BranchesWhat are Branches and Why Should We Use Them?
-
Branch Names
-
How to Create Branches
-
Using Pull Requests to Merge a Branch Into Main
-
Project Management with GitHubGitHub Issues
-
How to Organize Issues
-
Wrapping UpOther Cool Stuff You Can Do with GitHub
Lesson 15 of 26
In Progress
Why Use GitHub vs Dropbox, Google Drive, Box, etc?
Have any questions? Put them below and we will help you out!
You must be logged in to post a comment.
Assuming that this logic also applies to OneDrive? What about Sharepoint (using a form of OneDrive), which has version control?
I’ve never used Sharepoint’s version history myself, but I don’t think it’s going to match how robust GitHub is when it comes to version control. Being able to see where your all files at any point in your code’s history can be a big help when you’re trying to identify issues.