Skip to content

Instantly share code, notes, and snippets.

@JoshuaTPierce
Created June 7, 2017 17:21
Show Gist options
  • Save JoshuaTPierce/b919168421b40e06481080eb53c3fb2f to your computer and use it in GitHub Desktop.
Save JoshuaTPierce/b919168421b40e06481080eb53c3fb2f to your computer and use it in GitHub Desktop.
Creating and Pushing a R-Markdown Document to Github (including graphs)
Go to github
Create new repository [don't need to initialize with the readme (can add later)]
Go to R Studio
File -> New Project -> Version Control -> Git
Ctrl+V repository URL from GitHub
File -> New -> Markdown, enter Title, etc.
In the Markdown window, change "output=html_document" to "output=github_document"
Knit the document for the first time, will prompt you to save
Save as Title.rmd
In the "git" tab of the R studio Environment window, you will notice that the knit produced:
Title.rproj
Title.rmd
Title.md
Changing output to github_document makes the original .rmd knit to .md so the code can be rendered when pushed to Git.
In the Git window, check the box to stage Title.md [NOT .rmd]
Click "commit," add comment.
Click the green arrow to push to GitHub.
Go to GitHub, refresh the repository, and the markdown document with rendered code will be there
IF YOUR DOCUMENT INCLUDES GRAPHS:
When you knit, a new file will save to the Git window, called Title.docs
When you commit, check the box to stage the .docs in addition to the .md document.
This will commit the graphs as a separate file to the repository,
although the graphics will automatically pull in to the markdown document when rendered.
@SaumiRah
Copy link

SaumiRah commented Jun 6, 2023

Any advice on getting latex to render properly?

@amhoesk
Copy link

amhoesk commented Jun 11, 2023

Tnx. So helpful.

@dhumantorch
Copy link

dhumantorch commented Jul 30, 2023

For me, the graphs were stored in Title_files so I just added that instead of .docs. Worked anyway!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment