Get access to all lessons in this course.
Using Git and GitHub with R
Introduction to Git and GitHub
- What is Git? What is GitHub?
- Why Should You Learn to Use Git and GitHub?
- Update Everything
- Install Git
- Configure Git
- Create a Local Git Repository
- Commit History
- GitHub 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 GitHub
- Why 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
- What 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 GitHub
- GitHub Issues
- How to Organize Issues
- Other Cool Stuff You Can Do with GitHub
Dealing with Common Problems: Merge Conflicts
This lesson is locked
This lesson is called Dealing with Common Problems: Merge Conflicts, part of the Using Git and GitHub with R course. This lesson is called Dealing with Common Problems: Merge Conflicts, part of the Using Git and GitHub with R course.
Click on the transcript to go to that point in the video. Please note that transcripts are auto generated and may contain minor inaccuracies.
You should have a merge conflict in the README.md file because you edited it both in RStudio and on GitHub
Open up the README.md file and find the conflict markers, conflict divider, and identify which parts of the code come from the changes you made in RStudio and which come from the changes you made on GitHub
Edit the README.md file to resolve the merge conflict
Commit (I usually use a message like “fix merge conflict”)
Push your code to GitHub