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

Documentation #175

Merged
merged 38 commits into from
Feb 12, 2024
Merged

Documentation #175

merged 38 commits into from
Feb 12, 2024

Conversation

dgrassellyb
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@cicdguy cicdguy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Amazing 🤩

Copy link
Collaborator

@bms63 bms63 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ummm....whoa this is thorough!!!!!!! I will review tomorrow. 1.0 got me a little busy

@dgrassellyb
Copy link
Collaborator Author

I also made this cheatsheet (However some links need the documentation to be deployed)
But maybe still a bit complex to read !

Template cheatsheet.pdf

Copy link
Collaborator

@manciniedoardo manciniedoardo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dgrassellyb for this, this is fantastic!!

I left a few specific comments for typos and requests for clarification. I also have some comments about the front page README:

  • Many heading links in the readme don't work?
  • Full stop missing at the end of renv propagation section
  • Boilerplate or boilderplate? Could be a typo.
  • docker image build: typo in "each R version" (no "s" at the end)

I also have some general comments:

  • Within the navbar, for the User Guides section I would put a subsection titled "Basics" with the "Get Started", "Common structure of the workflows" and "Codespaces" sections. Then I would put another subsection titled "Invididual workflows" with all the other pages.
  • I would retitile "common structure" to "Common strucure of the workflows" and put it at the top of the articles.
  • There's also another "spell checks page" in the Articles drop down. Not sure what the difference is between the two?

vignettes/common_structure.Rmd Outdated Show resolved Hide resolved
vignettes/common_structure.Rmd Outdated Show resolved Hide resolved
vignettes/common_structure.Rmd Outdated Show resolved Hide resolved
vignettes/common_structure.Rmd Outdated Show resolved Hide resolved
vignettes/cran-status.Rmd Outdated Show resolved Hide resolved
vignettes/pkgdown.Rmd Outdated Show resolved Hide resolved
vignettes/push-docker.Rmd Outdated Show resolved Hide resolved
vignettes/r-cmd-checks.Rmd Outdated Show resolved Hide resolved

# Render README Workflow

This GitHub Actions workflow renders the README from R Markdown (`README.Rmd`) to Markdown (`README.md`). Additionally, it can format the generated Markdown using a formatter. The workflow is triggered manually (`workflow_dispatch`) and can also be invoked as a workflow call (`workflow_call`).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you specify why this is required?


# Spelling Workflow

This GitHub Actions workflow performs spellchecking on the specified R files. The workflow is triggered manually (`workflow_dispatch`) and can also be invoked as a workflow call (`workflow_call`).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mention somewhere the exclusion wordlist here?

@manciniedoardo
Copy link
Collaborator

manciniedoardo commented Dec 6, 2023

Can we add a hex to the front page too? smth like below

@manciniedoardo
Copy link
Collaborator

admiralci_logo

@dgrassellyb
Copy link
Collaborator Author

Thanks @dgrassellyb for this, this is fantastic!!

I left a few specific comments for typos and requests for clarification. I also have some comments about the front page README:

  • Many heading links in the readme don't work?
  • Full stop missing at the end of renv propagation section
  • Boilerplate or boilderplate? Could be a typo.
  • docker image build: typo in "each R version" (no "s" at the end)

I also have some general comments:

  • Within the navbar, for the User Guides section I would put a subsection titled "Basics" with the "Get Started", "Common structure of the workflows" and "Codespaces" sections. Then I would put another subsection titled "Invididual workflows" with all the other pages.
  • I would retitile "common structure" to "Common strucure of the workflows" and put it at the top of the articles.
  • There's also another "spell checks page" in the Articles drop down. Not sure what the difference is between the two?

Thanks a lot for your feedbacks, I will review this ! :)

@bms63
Copy link
Collaborator

bms63 commented Dec 6, 2023

I also made this cheatsheet (However some links need the documentation to be deployed) But maybe still a bit complex to read !

Template cheatsheet.pdf

above and beyond!!! This cheatsheet is so cool

@bms63
Copy link
Collaborator

bms63 commented Dec 6, 2023

Just a few notes:

Musing on the README - should we just remove most of the stuff there as it is discussed more thoroughly in the vignettes.

Get Started: Could this vignette get a separate tab?

Cheatsheet: Could that be linked as a Get Started dropdown option? Like how we have it on https://pharmaverse.github.io/admiral/dev/

Lock Files and Propagation: Since we are moving away from this - wondering if this is still need to document?

Copy link
Collaborator

@bundfussr bundfussr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great overall.

Maybe we should structure the "Articles" menu, e.g., separate sections for workflows used in all admiral packages and workflows used in admiralci only.

vignettes/get_started.Rmd Outdated Show resolved Hide resolved
vignettes/get_started.Rmd Outdated Show resolved Hide resolved
vignettes/get_started.Rmd Outdated Show resolved Hide resolved
vignettes/common_structure.Rmd Show resolved Hide resolved
vignettes/common_structure.Rmd Outdated Show resolved Hide resolved

### `multi-version-docs` Job

This job, if triggered, deploys the multi-version documentation to the `gh-pages` branch. It checks for the `skip-multiversion-docs` input and `[skip docs]` in the commit message before proceeding.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this job also update the "Versions" menu?

vignettes/propagate.Rmd Outdated Show resolved Hide resolved
vignettes/renv-lock.Rmd Outdated Show resolved Hide resolved
vignettes/spellchecks.Rmd Outdated Show resolved Hide resolved
vignettes/validation.Rmd Outdated Show resolved Hide resolved
@dgrassellyb
Copy link
Collaborator Author

@bms63 / @manciniedoardo / @cicdguy / @bundfussr : I am currently updating the doc (quite lot of changes since we removed renv !) - I just have a question about codespaces, our actual config is quite outdated (since we built it from renv dependencies) - I could work on this, but while it's not ready I was just thinking to tag the codespace section as "WIP article", what do you think ?

I guess codespaces feature is a bit low priority right ? (I am not sure if devs are really using it on admiral but let me know if I am wrong ! 🙊 )

I'd vote to keep at as a "WIP article" and get back to it later.

Ok let's do this ! it's ready to be merge now (I also pushed a fix in pkgdown to be able to push non-multi version documentation - because I guess we don't need multi version for admiralci doc !).
I also updated the cheatsheet here :
https://github.com/pharmaverse/admiralci/blob/documentation/vignettes/assets/cheatsheet.png

@bms63 bms63 marked this pull request as ready for review February 9, 2024 01:38
@bms63
Copy link
Collaborator

bms63 commented Feb 9, 2024

Shall we just merge and publish this and do the review in an issue? Might be a little easier if we don't have to pull down and render the site??

@dgrassellyb
Copy link
Collaborator Author

Shall we just merge and publish this and do the review in an issue? Might be a little easier if we don't have to pull down and render the site??

I'll fork it for rendering and send you the link

pharmaverse-bot and others added 2 commits February 9, 2024 09:39
* Update pkgdown.yml

* [actions skip] Add/Update README.md for main

* update cheatsheet

* update cheatsheet

* fix

* fix pdf rendering

* fix

* fix hex

* [actions skip] Add/Update README.md for main

* fix rendering

---------

Co-authored-by: GitHub Actions <[email protected]>
@dgrassellyb
Copy link
Collaborator Author

Pushed again some other fixs, here is the rendered doc from my forked repo : https://dgrassellyb.github.io/admiralci/
However .. I have an issue in r cmd checks for this PR - not sure to understand where it's coming from :

❯ checking CRAN incoming feasibility ... [1s/13s] NOTE
  Maintainer: ‘Open Source <[email protected]>’
  
  Found the following (possibly) invalid URLs:
    URL: 
      From: inst/doc/push-docker.html
      Message: Empty URL

0 errors ✔ | 0 warnings ✔ | 1 note ✖

I even updated the .Buildignore with ^inst/doc\.html$ but still get this

@cicdguy
Copy link
Collaborator

cicdguy commented Feb 9, 2024

@dgrassellyb That regex looks incorrect.
Should be ^inst\/doc\/.*.html$

reusable via the
[`workflow_call`](https://docs.github.com/en/actions/using-workflows/reusing-workflows)
GitHub Actions event.
reusable via the \[`workflow_call`]\[workflow\_call] GitHub Actions
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dgrassellyb is it that I don't understand what this syntax is saying or is it a typo? Don't be afraid to tell me if it's the former 😄

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed since to comes from .Rmd -> .md job, I have this in the .Rmd :

reusable via the [workflow_call][workflow_call] GitHub Actions event.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, thanks!

@manciniedoardo manciniedoardo self-requested a review February 9, 2024 16:13
@bms63
Copy link
Collaborator

bms63 commented Feb 9, 2024

Can we minimize this image please
image

@bms63
Copy link
Collaborator

bms63 commented Feb 9, 2024

Can we change the tab name to CI/CD Workflows
image

When I get a dozen tabs up be nice if I new which admiral to select??

@bms63
Copy link
Collaborator

bms63 commented Feb 9, 2024

What about removing these links and just listing out our potential workflows? The one I clicked go to 404.

image

Can we say why this is a bad practice? can't get latest and greatest updates - encourage you to make issues to enchance our workflows.

image

Could we give some context on what these bullet points are leading us to?

image

@bms63
Copy link
Collaborator

bms63 commented Feb 9, 2024

Possible to embed cheat sheet like we did for admiral?
image

Shall we remove devel references
image

Many thanks again!! Could be a really good reference for discussion for upcoming admiralpeds @rossfarrugia

@dgrassellyb
Copy link
Collaborator Author

Possible to embed cheat sheet like we did for admiral? image

Shall we remove devel references image

Many thanks again!! Could be a really good reference for discussion for upcoming admiralpeds @rossfarrugia

Thanks Ben I will apply some changes as you suggested (and also for your other comments above ;) )

@dgrassellyb
Copy link
Collaborator Author

What about removing these links and just listing out our potential workflows? The one I clicked go to 404.

image

Can we say why this is a bad practice? can't get latest and greatest updates - encourage you to make issues to enchance our workflows.

image

Could we give some context on what these bullet points are leading us to?

image

For the links it's not working because it's coming from my fork (if you replace on links pharmaverse by dgrassellyb it will work) - we won't have issues with links once it will be deployed in admiralci repo (non-forked one !) - I think it's nice to keep it (it's like a table of contents with redirections to detail documentation + workflows code)

@dgrassellyb dgrassellyb merged commit e48e3cf into main Feb 12, 2024
4 of 5 checks passed
@dgrassellyb dgrassellyb deleted the documentation branch February 12, 2024 13:43
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.

6 participants