Skip to content

Commit 8285526

Browse files
committed
add orcid libguide
1 parent 2dc4340 commit 8285526

File tree

12 files changed

+161
-2
lines changed

12 files changed

+161
-2
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
{
2+
"hash": "49960f42d440b8664619a04a44b69ece",
3+
"result": {
4+
"engine": "knitr",
5+
"markdown": "---\ntitle: \"Using the GitHub website\"\n---\n\n\nIn this section, we will be using the GitHub.com website and demonstrate that you do not need to be a programmer to use version control and edit files on GitHub.\n\n::: {.callout-note collapse=true}\n### Don't have a GitHub account?\n\nIf you have not already created a GitHub username, please do so now:\n\n- GitHub: <https://github.com>\n- Follow optional [advice on choosing your username](https://happygitwithr.com/github-acct.html)\n:::\n\n::: {.callout-tip}\n\n### Our asks\n\n### As a Team of two\n\n- Help each other, everyone is bringing different skills! Talk it out!\n- Listen to each other; avoid judgment and solutioneering.\n- Have fun!\n\n### Prompt\n\nWe want to log the information about people's favorite desserts using a repository.\n:::\n\n\n#### Person 1 (owner):\n\n- Create a repository using the following these [instructions](https://docs.github.com/en/github/getting-started-with-github/create-a-repo) steps 1-6\n\n![](img/github-dessert-repo.png)\n\n- Edit the README to:\n - Replace the title (first line starting with `#`) with something better! Maybe `Favorite Desserts`\n - Add your name and your favorite dessert below the title: e.g. ` - Julien: crepes`\n\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-readme_desserts.png){width=1248}\n:::\n:::\n\n\n- Add Person 2 as a collaborator following these [instructions](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)\n\n\n#### Person 2 (collaborator): \n\n- Check your email to accept the invitation\n- Go to the repository website (link is provided in the invitation)\n- Start editing the README.md by clicking on pen at the top of the README.md file to edit it\n\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-readme-edit.png){width=556}\n:::\n:::\n\n\n- Add your name and your favorite dessert below the title: e.g. ` - Sophia: chocolate`\n- Click _Commit changes_\n- Add a descriptive commit message, \"add my favorite dessert\"\n\n\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-commit.png){width=531}\n:::\n:::\n\n\n- Click _Commit changes_ to confirm\n\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-commit-button.png){width=20%}\n:::\n:::\n\n\n\n#### Person 1: add a file\n\nDownload this [csv file](https://aurora.nceas.ucsb.edu/~brun/favorite_desserts.csv) about your favorite desserts to your computer\n\n- Just drag and drop it on the Github web page of your repository to upload it\n- Add a short message about the file e.g. `Adding dessert csv` & hit `Commit changes`\n- Your have has been uploaded. Click on the filename to see it!\n\nYou should have something similar to this repo: <https://github.com/brunj7/favorite-desserts>\n\n\n#### Bonus \n\nPerson 2: Try to edit the csv file directly on GitHub! \n\nPerson 1: Your turn!\n\n**No need to be a programmer to contribute to analytical workflows with GitHub!!**\n\n\n",
6+
"supporting": [],
7+
"filters": [
8+
"rmarkdown/pagebreak.lua"
9+
],
10+
"includes": {},
11+
"engineDependencies": {},
12+
"preserve": {},
13+
"postProcess": true
14+
}
15+
}
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
{
2+
"hash": "fc689939176915d1068b4575b93b98a4",
3+
"result": {
4+
"engine": "knitr",
5+
"markdown": "---\ntitle: \"GitHub branches using RStudio\"\n---\n\n\n## Is your fav' dessert iconic !?!\n\nWrite and R script to compare the csv with your favorite desserts you modified previously with the top 42 most iconic American desserts \n\n1. Clone the repository you just created about your favorite desserts\n2. Create a new branch using RStudio and name it `*myinitials*_rstudio`\n3. Start a new script named `desserts_match_*myinitials*.R` \n4. As pair programming, write a script should read a csv file of your favorite dessert (create it if you do not have one yet) and the csv file with the most iconic desserts (see code below) into R and find out if your favorite dessert is part of the [most iconic desserts](https://www.eatthis.com/iconic-desserts-united-states/)!\n5. Push your changes to GitHub\n6. On the GitHub website, create a Pull Request (PR) and assign your teammate as reviewer\n7. Reviewer -- Review the PR. Make comments and/or OK the merge\n8. Requester -- Merge and close the PR \n\n\n\n::: {.callout-tip}\n### Code to get the iconic desserts listing\n\n\n::: {.cell}\n\n```{.r .cell-code}\nlibrary(tidyverse)\nlibrary(rvest) # use to scrape website content\n\n# Check if that data folder exists and creates it if not\ndir.create(\"data\", showWarnings = FALSE)\n\n# Read the webpage code\nwebpage <- read_html(\"https://www.eatthis.com/iconic-desserts-united-states/\")\n\n# Extract the desserts listing\ndessert_elements<- html_elements(webpage, \"h2\")\ndessert_listing <- dessert_elements %>% \n html_text2() %>% # extracting the text associated with this type of elements of the webpage\n as_tibble() %>% # make it a data frame\n rename(dessert = value) %>% # better name for the column\n head(.,-3) %>% # 3 last ones were not desserts \n rowid_to_column(\"rank\") %>% # adding a column using the row number as proxy for the rank\n write_csv(\"data/iconic_desserts.csv\") # save it as csv\n```\n:::\n\n:::\n",
6+
"supporting": [],
7+
"filters": [
8+
"rmarkdown/pagebreak.lua"
9+
],
10+
"includes": {},
11+
"engineDependencies": {},
12+
"preserve": {},
13+
"postProcess": true
14+
}
15+
}
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
{
2+
"hash": "2b6ed498af9afe2e3411e28fc282c1e4",
3+
"result": {
4+
"engine": "knitr",
5+
"markdown": "---\ntitle: \"GitHub workflows: forks and branches\"\n---\n\n\n### Setup\n\n#### Person 1 (owner):\n\n- Create a repository using the following these [instructions](https://docs.github.com/en/github/getting-started-with-github/create-a-repo) steps 1-6\n\n![](img/github-dessert-repo.png)\n\n- Add Person 2 as collaborator following these [instructions](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)\n- Edit the README to:\n - Replace the title (first line starting with `#`) with something better! Maybe `Favorite Desserts`\n - Add your name and your favorite dessert below the title: e.g. ` - Julien: crepes`\n\n\n::: {.cell}\n\n```{.r .cell-code}\nknitr::include_graphics(\"img/github-readme_desserts.png\")\n```\n\n::: {.cell-output-display}\n![](img/github-readme_desserts.png){width=1248}\n:::\n:::\n\n\n\n### Forks\n\n#### Person 2: Create a Fork\n\n- Ask your teammate to Slack you the link to the repository\n- Create a Fork by clicking on the Fork button on the top right view of your repository homepage\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-fork-button.png){width=60%}\n:::\n:::\n\n- On your Fork, start editing the `README.md` \n\n- Add your name and your favorite dessert below your teammate entry: e.g. ` - Sophia: chocolate`\n- Add a descriptive commit message\n\n\n::: {.cell}\n\n```{.r .cell-code}\nknitr::include_graphics(\"img/github-commit.png\")\n```\n\n::: {.cell-output-display}\n![](img/github-commit.png){width=531}\n:::\n:::\n\n\n- Commit your changes\n\n\n::: {.cell}\n::: {.cell-output-display}\n![](img/github-commit-button.png){width=20%}\n:::\n:::\n\n- Create a pull request to merge those changes to the main repository using these [instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)\n\n#### Person 1:\n\n- Go to *your* repository and merge the PR\n\n\n\n---\n\n### Branches\n\n#### Person 1: add a file\n\nDownload this [csv file](https://aurora.nceas.ucsb.edu/~brun/favorite_desserts.csv) about your favorite desserts to your computer\n\n- Just drag and drop it on the Github web page of your repository to upload it\n- Add a short message about the file: e.g. `Adding dessert csv` & hit `Commit changes`\n- Your file has been uploaded. Click on the filename to see it!\n\nYou should have something similar to this repo: <https://github.com/brunj7/favorite-desserts/blob/master/favorite_desserts.csv>\n\nNow you want to collaborate more closely and do not wan your teammate to have to create a fork and be able to work directly on your repository\n\n- Add Person 2 as a collaborator following these [instructions](https://docs.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)\n\n\n#### Person 2: Create a branch\n\n- Check your email or Github Notifications to accept the invitation\n- Go to the repository website (link is provided in the invitation)\n- Create a new branch named after your first name\n\n::: {.cell}\n\n```{.r .cell-code}\nknitr::include_graphics(\"img/github-create_branch.png\")\n```\n\n::: {.cell-output-display}\n![](img/github-create_branch.png){width=1148}\n:::\n:::\n\n- Edit the csv file directly on GitHub to add your favorite dessert to it \n- Create a **P**ull **R**equest (PR) to merge you branch back to main\n- Assign person 1 as a reviewer ([instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review))\n\n#### Person 1: Merge the branch\n\n- Review PR\n- Merge and close PR\n\n\n",
6+
"supporting": [],
7+
"filters": [
8+
"rmarkdown/pagebreak.lua"
9+
],
10+
"includes": {},
11+
"engineDependencies": {},
12+
"preserve": {},
13+
"postProcess": true
14+
}
15+
}

_freeze/git_cli/execute-results/html.json

Lines changed: 15 additions & 0 deletions
Large diffs are not rendered by default.

0 commit comments

Comments
 (0)