[x] Find other place to host embedded PDFs - CDPH blocks Google drive
CR Run through:
[x] Group workflow: still need to review section in the middle...
[x] About this training
[x] Why git and github
[x] Git Jargon page
[x] finish editing 5.2.1 at the end bad naming
[x] ON HOME COMPUTER DELETE THE MAY3 BRANCH FROM THE LE REPO SO CAN GRAB THE CORRECT CODE AFTER "WAS" AND REPLACE IN THE ABOVE. -- working solo section
[x] ADD THIS TO THE LE DATA FOLDER!: The new data file is the one called “LEbsyrx.csv” in the data folder
[ ] Add line breaks before new sections -- see the naming files page and see if we want to adopt that convention on all other pages
[ ] 9.2.2 image diff
[x] update location of iframe (cdph doesnt have access to google drive) - CORINNE AND LAUREN TO DISCUSS - CAN'T GET THIS TO WORK.
[x] embed survey link to course website after steph makes it - update stephanie will now send this via email right when the workshop finishes
[x] look at misc. page and make any edits!
[ ] look over solo workflow page
LBW Run through:
[x] Solo workflow
[x] Do’s and don’ts
[x] Why git and github
[x] Make the edits to setup that I had to stash
[x] Maybe make bullet changes if inspired
[x] Revise the git branching instructions from epi560 for this training (add as a pdf on the site)
[x] Screenshots into group workflow from collab session on thurs
[x] Take another stab at solo workflow polishing
[x] Odds and ends
[x] conclusions
[x] fix spelling mistake branching figure (successful "merged" to "merge" or change successful to successfully)
[x] forking: make the rightmost caption grey as well as the bracket symbol on the right that is currently salmon/coral. The caption for Lauren's repo is too small and maybe is a lighter shade but hard to tell. The right most caption is slightly too small as well. We have been using the solid circle to indicate a change so I think something needs to change in the figure to indicate that the first coral circle is a copy/clone/duplicate. Perhaps the solid line connecting them should have a label "Forked" or something like that, or the line type should be a double line... or the circle should be labeled with copy... brainstorming here, but need to do something. Consider also changing out the .R code or making the last change have more changes since it is a few points along the line away from when the repo was forked -- that needs to be communicated via more changes/differences and if it was really a fork then the data pathway should be different.
Both/together
[x] Direct edits decision
[x ] Turn slide vibes into website vibes
[x] Update two images on merge conflicts with correct colors and zooming in (first image too small)
Comments from LW to CR
01_whygit
[x] I am wondering if instead of subsections, everything should just be bold sections. E.g. ‘error reducing’, ‘version control facilitates reproducible analyses’, etc. should just be bold titles with a sentence beneath, rather than subsections. I left it for now, if you agree then you can change those to just be bold but unofficial section headers!
04_dos_and_donts
[x] How do you spell don’t’s ? the apostrophes are a bit odd
[x] I think the formatting here is better in prose form than bullets, but I do think we need some pictures or something to break it up. I’m not sure – take a look and see if you have ideas with fresh eyes!
06_git-cheat-sheet
[x] I added in a cheat sheet. Take a look! On our list of quality improvements is to make this a downloadable pdf!
03_solo_workflow
[x] I tried to make this more website format than bullets – let me know what you think!
[x] We walk through an example – are we going to make this publicly available? If so can you put links to download it into the site so that other users can replicate this and follow along?
[x] I put in ~3 comments for you to look at!
[x] This one is long – I think we should break it up with some screenshots or pictures or something to keep their attention! What do you think? Any ideas?
[x] Should we use the ‘bash’ coloring for the non-R code blocks particularly on this one or keep it gray/black? -- CR says: I feel like the bash coloring doesn't actually reflect the true bash coloring we see in terminal so I am not sure I want to use it anywhere. For example, in terminal all my commands are shown in black, but the output is sometimes shown in green or red, but this isn't accurately reflected in the bash coloring in R.
Overall/misc
[x] I think some titles are still too long, even of the overall pages. Take a look and shorten as you see fit if you agree!
[x] we called the site GitHub for Public health and I think we should call it Git for Public Health (the name int he top left when you load the page) - CR update: changed to Git and GitHub for PH (to be consistent with workshop title)
[ ] Add creative commons license to the website (by attribution, non commericial, share alike?)
[ ] Make pdf version of the website as a downloadable thing from the website?
[ ] break up agenda
Add odds and ends page [LW]
[x] Forking: bring up branching. Will be asked how it differs from branching - forking you may never want to merge back in. You are going off in another direction. -- fork the repo to have a starting point to go off and do your own things with, maybe without ever wanting to merge back in (give tangible example -- someone does analysi of X and Y, you are interested in Z and Y)
[x] git ignore: Open your .gitignore file in a text editor that you are comfortable with (e.g. nano or notepad). Add the following two lines to it:....
[x] rollback: CR removed this from the rollback section since nothing else on that page was technical. We can put this on some other page though: "To do this, you would search for the commit ID of the version you want to revert to and then use the git checkout {commit ID} command to revert to that version."
[x] make sure to mention that if all else fails, they should blow up their repo.
[x] add conclusion page [LW]
Nice to have/for SER:
[ ] Config package?
[ ] better forking image
[ ] missing space between 2 sentences at the bottom of "Naming folders..."
[ ] tell themn to save a bunch of times before committing!!
To discuss later
[ ] Pre commit hooks
CR to LW: You’ll see a URL that starts with https://. Push the icon with two overlapping squares to copy the URL to your clipboard. [Lauren, you had written this differently and had them use the SSH one… is there a reason to use one over the other?]
Important:
CR Run through:
LBW Run through:
01_whygit
04_dos_and_donts
06_git-cheat-sheet
Overall/misc
Add odds and ends page [LW]
[x] Forking: bring up branching. Will be asked how it differs from branching - forking you may never want to merge back in. You are going off in another direction. -- fork the repo to have a starting point to go off and do your own things with, maybe without ever wanting to merge back in (give tangible example -- someone does analysi of X and Y, you are interested in Z and Y)
[x] git ignore: Open your .gitignore file in a text editor that you are comfortable with (e.g. nano or notepad). Add the following two lines to it:....
[x] rollback: CR removed this from the rollback section since nothing else on that page was technical. We can put this on some other page though: "To do this, you would search for the
commit IDof the version you want to revert to and then use thegit checkout {commit ID}command to revert to that version."[x] make sure to mention that if all else fails, they should blow up their repo.
[x] add conclusion page [LW]
Nice to have/for SER:
To discuss later
CR to LW: You’ll see a URL that starts with https://. Push the icon with two overlapping squares to copy the URL to your clipboard. [Lauren, you had written this differently and had them use the SSH one… is there a reason to use one over the other?]