Sophie Charlotte Zeiz PU5058

[CharlotteZeiz]

Hello everyone! Please use this checklist over the next few weeks as you go through your health data science journey :tada:. Tick each item as your complete it!

---

Week 2: Your first repository

• [x] 1. Install GitHub desktop and connect it to your GitHub account
• [x] 2. Create a public repository and add a readme file
• [x] 3. Publish the repository to GitHub
• [x] 4. Add a new file in your local repository, commit the file addition, and push it to the remote repository on GitHub
• [x] 5. Modify the new file (or the Readme file), commit the change, and push it to the remote repository on GitHub
• [x] 6. Comment on this issue with a link to your repository

Week 4: Rmarkdown

• [x] 1. Create a new public repository on GitHub Desktop and add a readme file.
• [x] 2. Publish the repository to GitHub
• [ ] 3. Open RStudio and create a new project in an existing directory (the directory of your repository)
• [ ] 4. Download the file "R_Rstudio_Rmarkdown.Rmd" from the week 4 "Practical: R markdown" section on MyAberdeen and save it in your project
• [ ] 5. Work through the Rmarkdown file, remembering to commit and push your changes to the remote repository on GitHub
• [ ] 6. Optional: if you have questions you'd like to discuss with your group members, create issues on GitHub and let them know
• [ ] 7. Comment on this issue with a link to your new repository

Week 5: Practical: reading data in R

• [ ] 1. Create a new public repository on GitHub Desktop and add a readme file. This will be the main repository for the R material from this course, so give it a good name :smiley:
• [ ] 2. Publish the repository to GitHub
• [ ] 3. Open RStudio and create a new project in an existing directory (the directory of your repository)
• [ ] 4. Create an appropriate folder structure according to the good coding practices discussed in week 5
• [ ] 5. Download the data files and Rmarkdown file from the week 5 "Practical: reading data in R" section on MyAberdeen and save them in the appropriate folders in your project
• [ ] 6. Work through the Rmarkdown file, remembering to commit and push your changes to the remote repository on GitHub
• [ ] 7. Optional: if you have questions you'd like to discuss with your collaborators, create issues on GitHub and let them know
• [ ] 8. Comment on this issue with a link to your new repository

Week 6-10: Your project Now that you have become familiar with GitHub, you can start using it to prepare your report, and get help and feedback from your group members.

• [ ] Comment on this issue with a link to your report repository

[CharlotteZeiz]

This is the link to my repository.

https://github.com/CharlotteZeiz/Repo-IntroHDS-Charlotte

---

Step 4 and 5 where a bit confusing for me. I created a word document and added it in the web version github (via the add file button next to the green code button) Then i added a sentence to the document (in word) and pushed the change from the desktopversion. Was this the right way to do it? If i view the history now i can only see the version of the document with the extra senctence. I thought there would be the first version of the document as an anchorpoint like explained in the video. Can someone tell me what i did wrong? Thanks

[dblana]

Hi Sophie, the word document you added appears to be called "Add a new file in your local repository, commit the file addition, and push it to the remote repository on GitHub.docx"... is that right? As docx is a binary format, github cannot easily show the comparison of the different versions. If you used a text file (e.g. a markdown file with the extension .md - similar to the Readme file), you'd be able to see the comparison. But in terms of adding a file / making a change, you've done it correctly, well done! 🥳