Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

See if fetch-depth: 0 fixes the shallow problem #412

Merged
merged 5 commits into from
Jan 24, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/render-preview.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ jobs:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- name: Checkout files
uses: actions/checkout@v2
with:
fetch-depth: 0

# Set up git checkout
- name: Set up git checkout
Expand Down
4 changes: 3 additions & 1 deletion .github/workflows/style-and-sp-check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,9 @@ jobs:
steps:
- name: Checkout files
uses: actions/checkout@v2

with:
fetch-depth: 0

- name: login as jhudsl-robot
run: |
git config --local user.email "itcrtrainingnetwork@gmail.com"
Expand Down
6 changes: 4 additions & 2 deletions 02-chapter_of_course.Rmd
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@

# A new chapter

*If you haven't yet read the getting started Wiki pages; [start there](https://github.com/jhudsl/OTTR_Template/wiki/Getting-started)

Every chapter needs to start out with this chunk of code:
Expand Down Expand Up @@ -140,13 +142,13 @@ table of contents and enable the `scroll_highlight` feature
### Dropdown summaries

<details><summary> You can hide additional information in a dropdown menu </summary>
Here's more words that are hidden
Here's more words that are hidden.
</details>

## Print out session info

You should print out session info when you have code for [reproducibility purposes](https://jhudatascience.org/Reproducibility_in_Cancer_Informatics/managing-package-versions.html).

```{r}
sessionInfo()
devtools::session_info()
```