Skip to content

closes #384 new Roche council rep#385

Merged
rossfarrugia merged 2 commits into
mainfrom
384-new-roche-council-rep
Jun 4, 2026
Merged

closes #384 new Roche council rep#385
rossfarrugia merged 2 commits into
mainfrom
384-new-roche-council-rep

Conversation

@rossfarrugia

@rossfarrugia rossfarrugia commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

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!

@github-actions

github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Preview removed.

This PR has been closed and the preview website has been removed.

@rossfarrugia

Copy link
Copy Markdown
Contributor Author

@aaehmann, @ashley-tarasiewicz, @chrisprice-phuse - was quite sad writing this one, feels like the end of an era for me 😄
appreciate if it could be approved and merged by tomorrow if possible so i can put out some public comms on this.

FYI @shajoezhu

@aaehmann aaehmann left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This looks great! @rossfarrugia - you have been the driver of R adoption across the industry for so many years. Thank you for all that you do and have done - you have been a welcoming beacon within the community and I appreciate that!

@rossfarrugia rossfarrugia merged commit 0fb38d2 into main Jun 4, 2026
5 of 6 checks passed
@rossfarrugia rossfarrugia deleted the 384-new-roche-council-rep branch June 4, 2026 07:11
@shajoezhu

Copy link
Copy Markdown
Contributor

Thank you so much @rossfarrugia ! Thank you for everything that you have done for the community!

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.

4 participants