Skip to content

Commit

Permalink
Updates to early setup
Browse files Browse the repository at this point in the history
  • Loading branch information
jennybc committed Jun 17, 2022
1 parent 706b41b commit a64039a
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 7 deletions.
6 changes: 3 additions & 3 deletions connect-git-github.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@ Objective: make sure that you can pull from and push to GitHub from your compute

I do not explain all the shell (Appendix \@ref(shell)) and Git commands in detail.
This is a black box diagnostic / configuration exercise.
In later chapters and in live workshops, we revisit these operations with much more narrative.
In later chapters and in live workshops, we revisit these operations with much more narrative and discussion of alternative workflows.

I assume you've decided whether to use HTTPS (see chapter \@ref(https-pat) or SSH (see chapter \@ref(ssh-keys)) and you've prepared your credential.
I assume you've decided whether to use HTTPS (see chapter \@ref(https-pat)) or SSH (see chapter \@ref(ssh-keys)) and you've prepared your credential.

## Make a repo on GitHub

Expand All @@ -30,7 +30,7 @@ cat(res, sep = '\n')

## Clone the repo to your local computer

We have a few ways to do this: with command line Git or via RStudio.
We have a few ways to do this: with command line Git or via RStudio (or, eventually, usethis).

### Clone with command line Git

Expand Down
10 changes: 6 additions & 4 deletions connect-rstudio-git-github.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -18,10 +18,14 @@ We assume the following:
* You've confirmed that you can push to / pull from GitHub from the command line (chapter \@ref(push-pull-github)).

You will also need a test repository on GitHub.
If you don't have a suitable test repository on GitHub, follow the instructions in the next section.

If you just completed the previous chapter, [Connect to GitHub], that will be perfect!
If you just completed the previous chapter, [Connect to GitHub], that repo will be perfect!
However, I encourage you to delete the *local* repository, so you can experience how we use RStudio to clone it and get a local copy.
Delete the folder corresponding to the local repo any way you like.
This is a actually a workflow we refer to elsewhere (see \@ref(burn) as "burn it all down".
It's a deeply pragmatic coping strategy if your local Git repo is goofed up, but the version on GitHub is pretty current.

Delete the folder corresponding to the **local repo** any way you like.
It's just a regular directory on your computer.
Here's how to do that in the shell, if current working directory is `myrepo`:

Expand All @@ -30,8 +34,6 @@ cd ..
rm -rf myrepo/
```

If you don't have a suitable test repository on GitHub, follow the instructions in the next section.

## Make a repo on GitHub

```{r echo = FALSE, results = "asis"}
Expand Down

0 comments on commit a64039a

Please sign in to comment.