index.qmd

---
pagetitle: "PharmaDevOps"
page-layout: custom
section-divs: false
editor: source
sidebar: false
search: false
description: The home of the PharmaDevOps PhUSE Working Group.
image: assets/PharmaDevOps.png


listing:
  - id: cicdworkflows-minimum
    contents:
    - /content/cicdworkflows-minimum
    - "!index.qmd"
    sort: "date desc"
    type: grid
    categories: true
    sort-ui: false
    filter-ui: false
    max-items: 24
    feed: false
  - id: cicdworkflows-recommend
    contents:
    - /content/cicdworkflows-recommend
    - "!index.qmd"
    sort: "date desc"
    type: grid
    categories: true
    sort-ui: false
    filter-ui: false
    max-items: 24
    feed: false
  - id: cicdworkflows-enhanced
    contents:
    - /content/cicdworkflows-enhanced
    - "!index.qmd"
    sort: "date desc"
    type: grid
    categories: true
    sort-ui: false
    filter-ui: false
    max-items: 24
    feed: false

toc: false
---

<!--# Top welcome box -->

::: {.content-container}
::: {.top-story .blue-background}

::: grid
::: {.g-col-12 .g-col-lg-8 .top-story-text}
## Welcome to the home of **PharmaDevOps**
This PHUSE working group is  focussed on ensuring R package authors new
to concepts like CICD can
can easily add these useful automations to pharmaverse R packages
and related biostatistical packages.

We hope to both
convince package developers of the value of CICD,
provide a minimum bar of what is expected, and provide a
set of tools to make it easy to implement.
:::
::: {.g-col-12 .g-col-lg-4 .top-story-img}
![](assets/PharmaDevOps.png){width=70% fig-align="center"}
:::
:::

:::
:::

<!--# Notes on getting started -->
::: {.content-container}
::: {.top-story}

::: grid
::: {.g-col-12 .top-story-text}
## Getting started with CICD

In this guidance, you'll see a number of `gh-actions` that you can use to implement CICD on your project. We have categorised these into three groups:

- *Minimum CICD*: These are the minimum CICD tools we recommend for all packages, including those in the `pharmaverse` and `openstatsware`. These CICD tools are focussed on ensuring your package works, and the documentation users see matches the latest release of your code.
- *Recommended CICD*: These are tools we feel make your life developing and releasing robust code easier.
- *Enhanced CICD*: These are tools are option tools for power users, or those with specific needs.

Each CICD action is described via a common pattern, with an emphasis on why we recommend it, and how to use it.

A recomended plan for success in implenting CICD on your project is to:

- [Read this post](post/posts/gh-actions.html) on the general anatomy of a `gh-action`
- Browse our recomended `gh-action`'s below
- Implement CICD on your git repo!

We've also collected togther [this list of external learning resources](post/posts/external-resources.html).

:::
:::

:::
:::


<!--# Latest add-gh actions -->

::: {.content-container}
::: {.listing-block}
<a href="/content/cicdworkflows-minimum/index.qmd">

## Minimum CICD

The following CICD is what we consider a minimum bar for a
package on the pharmaverse. These CICD tools are focussed on
ensuring your package works, and documentation matches the code.

There is no need to use the specific code we suggest, if you are happy getting
the same functionality from another source, like the ones
built into `usethis`.


</a>

::: {#cicdworkflows-minimum}
:::

:::
:::

::: {.content-container}
::: {.listing-block}
<a href="/content/cicdworkflows-recommend/index.qmd">

## Recommended CICD

The following CICD are tools we feel make your life developing and
releasing robust code easier.

</a>

::: {#cicdworkflows-recommend}
:::

:::
:::

::: {.content-container}
::: {.listing-block}
<a href="/content/cicdworkflows-enhanced/index.qmd">

## Enhanced CICD

The following CICD are tools are optional tools for power users.

</a>

::: {#cicdworkflows-enhanced}
:::

:::
:::