Skip to content

Closes #391 Blog Post: risk.assessr - #392

Draft
Edward-Gillian0427 wants to merge 5 commits into
mainfrom
391-blog-post-riskassessr
Draft

Closes #391 Blog Post: risk.assessr #392
Edward-Gillian0427 wants to merge 5 commits into
mainfrom
391-blog-post-riskassessr

Conversation

@Edward-Gillian0427

@Edward-Gillian0427 Edward-Gillian0427 commented Jun 23, 2026

Copy link
Copy Markdown
Collaborator

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.

Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

  • Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
  • Ensure your new post folder is of the form "posts/date_with_short_tile" and the blog post file and any other artifacts have informative but succinct names.
  • Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
  • Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Python", "Community", "Conferences", "Submissions", "Technical", "DEI") for your blog post. If you cannot find anything that fits your blog post, propose a new tag to the maintainers! Note: if you use a tag not from this list, the "Check Post Tags" CICD pipeline will error. We occasionally tidy up all tags for consistency.
  • Add a short description for your blog post in the description field at the top of the markdown document.
  • Blog post is short, personalized, reproducible and readable
  • Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
    This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
  • Address all merge conflicts and resolve appropriately
  • Assign two of us (@aaehmann, @ashley-tarasiewicz, @chrisprice-phuse) as reviewers in the PR.
  • Pat yourself on the back for a job well done! Much love to your accomplishment!

@Edward-Gillian0427 Edward-Gillian0427 linked an issue Jun 23, 2026 that may be closed by this pull request
@Edward-Gillian0427
Edward-Gillian0427 marked this pull request as draft June 23, 2026 14:19
Comment thread posts/2026-06-23-risk-assessr-a-data/risk-assessr-a-data.qmd
Comment thread posts/2026-06-23-risk-assessr-a-data/risk-assessr-a-data.qmd Outdated
@aaehmann

Copy link
Copy Markdown
Collaborator

Hi @Edward-Gillian0427 - there are still checks failing and I will check them tomorrow.

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.

Blog Post: risk.assessr

2 participants