Closed jjc2718 closed 1 year ago
cansavvy
commented
1 year ago Oh. While I appreciate that you forked this repository, because I imagine you were trying to keep your edits sequestered; the OTTR checks can't run on forked repositories (I wish it could -- I've been looking for a solution to this). So that's what's going on here.
jjc2718
commented
1 year ago Oh. While I appreciate that you forked this repository, because I imagine you were trying to keep your edits sequestered; the OTTR checks can't run on forked repositories (I wish it could -- I've been looking for a solution to this). So that's what's going on here.
Got it - I was going to ask you tomorrow, but that's what I was guessing was going on. I'll move my changes to a branch of the main repo and re-open this PR. Thanks!
Purpose/implementation Section
What changes are being implemented in this Pull Request?
Adding a chapter that introduces good programming practices and how they relate to scientific software development, and a short intro to how automation fits in.
Tell potential reviewers what kind of feedback you are soliciting.
Any feedback would be great! Structure, text, concepts I'm missing, etc.
New Content Checklist
[x] New content/chapter is in an Rmd file with this kind of format and headers.
[x] New content/chapter contains learning objectives.
[ ] Bookdown successfully re-renders and any new content files have been added to the _bookdown.yml.
[ ] Spell check runs successfully).
[x] Any newly necessary packages that are needed have been added to the Dockerfile and image.
[x] Images are in the correct format for rendering.
[x] Every new image has alt text and is in a Google Slide.
[x] Each slide is described in the notes of the slide so learners relying on a screen reader can access the content. See https://lastcallmedia.com/blog/accessible-comics for more guidance on this.
[ ] The color palette choices of the slide are contrasted in a way that is friendly to those with color vision deficiencies. You can check this using Color Oracle.