generated from jhudsl/OTTR_Template_Website
-
Notifications
You must be signed in to change notification settings - Fork 0
/
setup.Rmd
133 lines (83 loc) · 5.28 KB
/
setup.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
---
title: "Setup"
output: html_document
---
### Getting started
Create your repository by clicking on the `Use this Template` button at [OTTR_Template_Website repository](https://github.com/jhudsl/OTTR_Template_Website)
You'll need to make your repository `public`.
### Set your GH_PAT
To enable the GitHub actions, your repository needs to be setup in a specific way.
For OTTR GitHub actions to run, they need to have credentials through a personal access token.
1. Set up your own personal access token [following these instructions](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) - but create a **classic token**. Keep this personal access token handy for the next step. When you get to the permissions page, check the box that says `repo` and select all that is underneath that header. No other permissions are necessary.
<details><summary>Click here for more detailed instructions. The instructions for this step may change with updates to GitHub.</summary>
First, go to your username settings, by clicking on your user icon (upper right corner) and scrolling down to settings.
```{r, fig.align='center', fig.alt= "User settings", echo = FALSE, out.width="20%"}
knitr::include_graphics("resources/images/usersettings.png")
```
Next, scroll all the way down on the far right menu to "Developer Settings".
```{r, fig.align='center', fig.alt= "User settings", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/developer_settings.png")
```
Then select "Personal Access Tokens" and "Tokens (classic)"
```{r, fig.align='center', fig.alt= "classic tokens", echo = FALSE, out.width="40%"}
knitr::include_graphics("resources/images/classic_tokens.png")
```
Then click "Generate new token" and confirm that you want classic.
```{r, fig.align='center', fig.alt= "generate classic token", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/generate_classic.png")
```
Finally, add a name select all the repo scopes and scroll down to the green button to generate the token. Copy this somewhere safe to then paste into your repository settings.
```{r, fig.align='center', fig.alt= "set up token", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/set_up_token.png")
```
</details>
2. In your new OTTR_Template_Website derived repository, go to Settings > Secrets and variables > Actions. Click `New Repository Secret`.
```{r, fig.align='center', fig.alt= "classic tokens", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/repo_action_token.png")
```
```{r, fig.align='center', fig.alt= "new repository secret", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/gh_pat_set_up.png")
```
In the window opened, name this new secret `GH_PAT` and paste the personal access token in the box below. (Note that the name `GH_PAT` is specific to how OTTR works and other secret names cannot be used and for OTTR to still work).
Click the green button to add the secret.
```{r, fig.align='center', fig.alt= "Clicking on settings", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/setting_gh_pat.png")
```
### Allow GitHub Actions
Go to the settings menu for your repository that you created from the template. This should be located at the top of GitHub on the right side.
Scroll down to the "Actions" button and click it, then click "General".
```{r, fig.align='center', fig.alt= "allowing workflows", echo = FALSE, out.width="40%"}
knitr::include_graphics("resources/images/actions.png")
```
```{r, fig.align='center', fig.alt= "allowing workflows", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/general.png")
```
Scroll down to the workflow permissions section and select "Read and write permissions", then click "Allow GitHub actions to create and approve pull requests.
Finally, click "save".
```{r, fig.align='center', fig.alt= "allowing workflows", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/workflows.png")
```
### Protect branches
Although this isn't entirely required, its strongly recommended that you use these settings to protect your `main` branches.
Click on settings in the far upper right corner:
```{r, fig.align='center', fig.alt= "Clicking on settings", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/settings.png")
```
Click on branches:
```{r, fig.align='center', fig.alt= "Clicking on settings", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/branches.png")
```
Click the add rule button.
```{r, fig.align='center', fig.alt= "Adding rule", echo = FALSE}
knitr::include_graphics("resources/images/add_rule.png")
```
Type "main" as the branch name pattern:
```{r, fig.align='center', fig.alt= "adding main branch rule", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/main_branch.png")
```
Click on the following boxes to require pull requests before merging:
```{r, fig.align='center', fig.alt= "modify branch rules", echo = FALSE, out.width="80%"}
knitr::include_graphics("resources/images/branch_rule.png")
```
Note that if you have admin privileges on this repository, you will likely still be able to override these branch protections so use caution when git pushing!