Skip to content

Commit 6f72973

Browse files
authored
Merge pull request #524 from avancra/add-rstudio-merging
Add RStudio path to merging.md - Fix #500
2 parents 971c3c0 + c0d6e6d commit 6f72973

1 file changed

Lines changed: 50 additions & 2 deletions

File tree

content/merging.md

Lines changed: 50 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Illustration of what we want to achieve in this exercise.
4545
:::
4646

4747

48-
We offer **three different paths** of how to do this exercise. For
48+
We offer **four different paths** of how to do this exercise. For
4949
the CodeRefinery workshop day 1, we use and demonstrate the **GitHub
5050
path** only and recommend you do that. The exercise text below has
5151
some GitHub-specific notes, but most is possibly with any path.
@@ -97,7 +97,7 @@ We provide basic hints. You should refer to the solution as needed.
9797
:::
9898
::::
9999

100-
::::{group-tab} Local (VS Code, Command line)
100+
::::{group-tab} Local (VS Code, Command line, RStudio)
101101

102102
When working locally, it's easier to merge branches: we can just do
103103
the merge, without making a pull request. But we don't have that step
@@ -161,6 +161,12 @@ This is different from the GitHub path:
161161
$ git switch main
162162
```
163163
::::
164+
165+
::::{group-tab} RStudio
166+
Remember, you need to switch to the `main` branch, the branch we want to merge **to**.
167+
This is different from the GitHub path.
168+
::::
169+
164170
:::::
165171

166172

@@ -193,6 +199,13 @@ we don't cover that here.
193199

194200
If you are working locally, continue to step 5.
195201
::::
202+
::::{group-tab} RStudio
203+
It is possible to open pull requests from the terminal, but
204+
we don't cover that here.
205+
206+
If you are working locally, continue to step 5.
207+
::::
208+
196209
:::::
197210

198211

@@ -227,6 +240,11 @@ If you are working locally, continue to step 5.
227240
::::{group-tab} Command line
228241
If you are working locally, continue to step 5.
229242
::::
243+
244+
::::{group-tab} RStudio
245+
If you are working locally, continue to step 5.
246+
::::
247+
230248
:::::
231249

232250

@@ -259,6 +277,15 @@ we don't cover that here.
259277

260278
If you are working locally, continue to step 5.
261279
::::
280+
281+
::::{group-tab} RStudio
282+
It is possible to create pull requests from the terminal, but
283+
we don't cover that here.
284+
285+
If you are working locally, continue to step 5.
286+
::::
287+
288+
262289
:::::
263290

264291

@@ -304,6 +331,12 @@ In this case we merge the `new-recipe` branch into our current branch:
304331
$ git merge new-recipe
305332
```
306333
::::
334+
335+
::::{group-tab} RStudio
336+
This doesn't seem possible in RStudio without an add-in. We recommend that you use the Terminal in RStudio and follow
337+
the "Command line" path instructions.
338+
::::
339+
307340
:::::
308341

309342

@@ -364,6 +397,12 @@ $ git branch
364397
$ git log --oneline
365398
```
366399
::::
400+
401+
::::{group-tab} RStudio
402+
This doesn't seem possible in RStudio without an add-in. We recommend that you use the Terminal in RStudio and follow
403+
the "Command line" path instructions.
404+
::::
405+
367406
:::::
368407

369408

@@ -400,6 +439,15 @@ lesson](https://coderefinery.github.io/git-collaborative/).
400439
You would create a new branch locally like above, {term}`push` it to GitHub to your own user's repository `USER/recipe-book`, then go to GitHub and open a pull request *to* `cr-workshop-exercises/recipe-book`.
401440

402441
::::
442+
443+
::::{group-tab} RStudio
444+
Not described. We will return to this in the [collaborative Git
445+
lesson](https://coderefinery.github.io/git-collaborative/).
446+
447+
You would create a new branch locally like above, {term}`push` it to GitHub to your own user's repository `USER/recipe-book`, then go to GitHub and open a pull request *to* `cr-workshop-exercises/recipe-book`.
448+
449+
::::
450+
403451
:::::
404452

405453

0 commit comments

Comments
 (0)