forked from RVerse-Tutorials/RWorkflow-NWFSC-2021
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathweek7-more-git.Rmd
185 lines (120 loc) · 10.4 KB
/
week7-more-git.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
---
title: "Week 7: More Git"
output:
html_document:
toc: true
include:
after_body: footer.html
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```
```{r echo=FALSE, message=FALSE, warning=FALSE}
library(kableExtra)
dt <- data.frame("Compartmentalized", "Documented", "Extendible", "Reproducible", "Robust")
kable(dt, col.names=NULL) %>%
kable_styling(full_width = TRUE) %>%
row_spec(1, bold = FALSE, color = "white", background = "blue") %>%
column_spec(column = 1:5, width = "20%")
```
This week I will cover some more features of using Git, GitHub, and RStudio. Although I'll be using GitHub, the same workflow applies to GitLab. I am going to be using GitHub Desktop to interact with GitHub since I find that GitHub Desktop helps me deal with merge conflicts and reverts (getting rid of changes I have made).
* What's a merge conflict and how to fix it
* How to use branches
* How to do a pull request to pull a branch into your master repository
* How to 'go back in time' and get rid of changes
* Working with issues in GitHub
* How to create a release in GitHub
* A workflow to minimize headaches
I'll be illustrating this with this repo: https://github.com/eeholmes/MyNewPackage
You can see a real-world example of this here on my MARSS package repo:
https://github.com/nwfsc-timeseries/MARSS
## Merge conflicts
Merge conflicts happen when there are changes to a file on your remote repository (GitHub or GitLab) but also changes to that same file on your local repository. Git doesn't know how to resolve the conflicting changes and needs your help.
### Resolving these with GitHub Desktop
GitHub Desktop makes resolving these pretty easy.
1. If it tells you to fetch commits off GitHub, go ahead and do that.
2. Now try to Pull. It'll tell you that you have conflicts and give you options for what to do.
* Click the 'x' and Git will alter `hello.R` and show where the conflicts are. You then edit `hello.R` in RStudio to fix the conflicts.
* If you know what file you want to use, use the little arrow dropdown to use the file on GitHub or on your local machine.
* Use Abort Merge to abandon the merge. Your changes to `hello.R` are still there.
* Click on History, right click the commit and revert to get rid of it. All file changes that are part of that commit will disappear! You can revert the revert if needed.
* Go into `hello.R` and fix the conflict. Git won't have marked it so it might be hard to find.
### Resolving these with Git in RStudio
Unfortunately, when you hit 'Push' in the Git tab in RStudio, it will immediately change `hello.R` with the conflicts. RStudio won't give you the chance to abandon the merge or pick one of the files.
But you can fix and then merge.
* Open `hello.R` and get rid of all the merge conflict code (denoted with the ============ and >>>>>>>>>>>>>>>>).
* The file will appear in the Git tab.
* Click on the checkbox until a CHECK appears. Filled in square is not enough. You need the CHECK.
* Commit the change.
* Push.
## Working with branches
Why use branches?
* Let's say you have a function that works fine and you want to make a bunch of changes but don't want to break the old version. Work on a branch to sandbox your changes and merge back into master when done.
* Let's say you want to try out an idea or new feature. Develop on a branch and merge into master when done.
* Let's say you want to do a major revamp of your code, but you are worried that you might want to abandon this. Work on a branch. If you decide against the change, you just delete the branch.
* Will your work break code? Make a branch.
When you start, keep it simple. Use a branch for one file or two. Work on the file and then merge it back into master. Then get rid of the branch. It's not necessary to use branches but if you do a lot of coding or work on packages, then getting comfortable with them will help you out.
### Make a new branch in RStudio
Click the new branch icon and give your branch a name. Give it an INFORMATIVE name. `tmp`, `foo` are bad. `hello_branch` is good as it tells what this branch is for (working on the `hello.R` file).
Now that you have a branch, it is critical that you pay attention to the Git tab and know where you are working. RStudio will remember what branch you are on.
Let's make a change to `hello.R` on hello_branch, put to GitHub and see what the two branches look like.
### Pull request, merge our branch with master
There are a few ways to do a pull request.
* You can do it from GitHub Desktop. It'll just redirect you to GitHub however.
* You can do it from GitHub.
Once you have created the pull requests, you'll see that the pull request tab (in GitHub) shows that there is a request.
* Click on the request. You have 2 options.
* Close it (don't merge). If you close it, you can reopen it later.
* Merge the request.
* You have done the merge on GitHub. You still need to do a Pull to get that change into your local repository.
* Delete your branch when you are done with it. All the history is saved. There is no reason keep branches that you are done with.
### Branch actions from GitHub Desktop
The branch toolbar in GitHub Desktop let's keep branches up to date with each other.
Let's say I am working on `littleforecast.R` in the master branch while working on `hello.R` in the hello_branch. I want to keep these synced up.
* **Compare** I can compare branches and look at the differences.
* **Merge into current branch** I can merge changes from one branch into another branch. It will let you see the changes before you decide to merge.
* **Update from master** This immediately merge changes from master into your branch. It won't ask you. So you need to revert the change if you don't like it.
This is similar to a pull request but happening locally. When a team is working on different branches, they would use pull requests.
### Branch actions from GitHub
You can do the same actions from GitHub.
## Issues
* Use the Issues in GitHub to enter any issues (bugs, feature changes, notes).
* You can reference issues in your commits with #<num of the issue>
* Add code to your issue so you can easily recreate the problem
## Releases
* The release or tag feature in GitHub will help you go back in time and document working states
* Use a NEWS file to keep a notebook of all your changes. I use a standard format with BUGS, DOCUMENTATION, ENHANCEMENTS. It's really helpful for understanding what is happening with the code.
## Getting rid of changes you have made
Say you made a change and you need to get rid of that. The temptation (for me) is to jump onto the Git command line and clobber my repository with `reset` and `revert` commands. Don't do this. Here are some strategies that will make this let prone to leaving your code a mess.
### Have you commited the changes yet?
**No?** Easy click on the file in the Git panel in RStudio, right click, and click 'Revert'. Note this will take things all the way back to your last commit!! If you have been making a bunch of changes without committing those, then you are out of luck.
**Yes?** Go to History in the GitHub Desktop window, click on the commit and click 'Revert'. This will get rid of all the changes that went with that commit. So if you changed multiple files, all those files will be reverted. If you have pushed the changes to GitHub, then you can push the revert and it'll show up on GitHub too.
**Yes but you just want to revert one file in a multi-file commit?** Ok, you can do this at the Git command line, but I find that to be a huge time suck and in my early Git days, I sometimes left my repository with a horrible problem that I could not fix and had to completely rebuild my repo. Since I don't need to be a Git wizard, this is what I do when I want to go 'back in time' for a since file.
Assuming you have already pushed the changes up to GitHub
* Go to the repo on GitHub
* Click 'commits' It's a little icon above your code with a clock with a counter-clockwise arrow.
* Scroll to the commit where the file was in the state you want (one before the last bad commit).
* On the right click the `< >` to browse your repo at the state in time where your file was ok.
* Click on the file and copy the text.
* Go back to RStudio, open the file, and paste in the text from when it was good.
If you have not pushed the changes up to GitHub.
* Now you have to go to the Git command line. Git tab in RStudio and then click the cog > Shell.
* Note, in 9 times out of 10, I would push the commit to GitHub and then use the above copy/paste to avoid using the Git command line. I would find that much faster.
Ok, here's the Git command to get a single file back. This works whether or not you have pushed to GitHub. The problem with this and why I don't do it is that I usually need to look at the file. So I am scrolling back through the status of my repo in the past until I find the status that I want. Then I stare a bit and think and think. Then get a coffee and think some more. Then I scroll back through the status of the repo in the past some more and THEN I do the copy and paste. It is rarely the case that I know exactly what commit that I need to get rid of---and even rarer that I want to go completely to a status in the past.
* Open the Git bash shell
* `git log` to find the commit hash (the long number)
* `git checkout 1d0f8c2eb4e66db0a7123588ae2fad26a6338303~1 -- ./R/test.R` would reset test.R to one before that commit. This part `1d0f8c2eb4e66db0a7123588ae2fad26a6338303` is the bad commit hash and this part `~1` means what the file was like 1 commit before that.
If you accidentally leave off the file name and Git says you have a detached head, use `git checkout master` to reattach your head.
## A workflow to minimize headaches
### Starting out
* Don't use branches when you are just starting. Get used to committing and pulling without creating merge conflicts.
* Get in the habit of always doing a Pull/Push before you start work in your project.
### Once you are experienced with GitHub
Once doing commits and push/pulls is familiar and you are no longer messing up your repository or making merge conflicts,
* Start using branches
* Work on one branch at a time
* Delete your branch when done
* Once you start using multiple branches, be careful to keep them separate. Modifications to `file_xyz` should only be in one branch.