Skip to content

Apply new tutorial template#394

Merged
NeuroShepherd merged 22 commits into
mainfrom
393-apply-new-template
Jul 22, 2026
Merged

Apply new tutorial template#394
NeuroShepherd merged 22 commits into
mainfrom
393-apply-new-template

Conversation

@NeuroShepherd

Copy link
Copy Markdown
Member

No description provided.

@NeuroShepherd NeuroShepherd linked an issue Jul 21, 2026 that may be closed by this pull request
@NeuroShepherd

Copy link
Copy Markdown
Member Author

Images needing updates by chapter:

fork

  • none

clone

  • picture 6, RStudio

commit to a project

  • none

push

  • none

pull Request

  • picture 1, github (not really necessary though)

merge changes

  • none

pull

  • none

Comment thread plot_trait_evolution.Rmd
@NeuroShepherd
NeuroShepherd requested a review from MalikaIhle July 21, 2026 10:36
@NeuroShepherd

NeuroShepherd commented Jul 21, 2026

Copy link
Copy Markdown
Member Author

Summary:

  1. Site renders correctly still
  2. Images are all visible and only 1 or 2 should be updated for the new repo structure
  3. The folder containing all of the R scripts, params/, has been left untouched. It is still at the root of the project, and none of the files have been renamed so all instructions/download info still applies
  4. Users trying to visit old HTML paths are redirected to the correct new page with the use of the aliases: yaml field

@NeuroShepherd

NeuroShepherd commented Jul 21, 2026

Copy link
Copy Markdown
Member Author

@MalikaIhle to confirm, the workflow of this tutorial is like this:

  1. Students clone/fork repo
  2. Students make edits on their fork, and open a PR in this repo
  3. You merge their PRs into main
  4. You git pull the changes on main
  5. You render the updates locally to show the students (and going forward, can just run quarto preview)

Is this generally correct?

@MalikaIhle

Copy link
Copy Markdown
Member

@MalikaIhle

Copy link
Copy Markdown
Member

@MalikaIhle to confirm, the workflow of this tutorial is like this:

  1. Students clone/fork repo
  2. Students make edits on their fork, and open a PR in this repo
  3. You merge their PRs into main
  4. You git pull the changes on main
  5. You render the updates locally to show the students (and going forward, can just run quarto preview)

Is this generally correct?

1-2 yes they should only add a new R file within param folder.
3. yes, simple merge, not sqaush merge or protection on main or anytthing, just merge
4. yes
5. no I only render the one Rmd (which now seems to be a QMD). this calls the files in the params folde. I believe it needs to be in the root of the project for this to work. I do not need the Rmd/QMD of the exercice to be on the website (it is not linked as such there)

@MalikaIhle

Copy link
Copy Markdown
Member

what is this?
image
could this be removed?

@MalikaIhle

Copy link
Copy Markdown
Member
  • rendering the exercice QMD file alone works
  • previewing locally works

@NeuroShepherd

Copy link
Copy Markdown
Member Author

what is this? image could this be removed?

Can you try deleting _site and then running quarto preview again to see if that persists? It's not present for me, and might just be a caching issue of some sort

@NeuroShepherd

NeuroShepherd commented Jul 21, 2026

Copy link
Copy Markdown
Member Author

I just rendered this branch to our live site to double-check https://lmu-osc.github.io/Collaborative-RStudio-GitHub/, and there is no issue there

@MalikaIhle

Copy link
Copy Markdown
Member

what is this? image could this be removed?

Can you try deleting _site and then running quarto preview again to see if that persists? It's not present for me, and might just be a caching issue of some sort

I just did that but it is still there for me (maybe a RStudio thing?)

@MalikaIhle

MalikaIhle commented Jul 21, 2026

Copy link
Copy Markdown
Member

on my side I've made the 3 commits I needed. ready to merge. perhaps the weird dispaly thing will not be on the website anyway, just on my local envt.

@NeuroShepherd

Copy link
Copy Markdown
Member Author

Will close #304 and #387

Comment thread matomo-analytics.html
@NeuroShepherd
NeuroShepherd merged commit 6f0a598 into main Jul 22, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Apply new template

2 participants