We as members, contributors, and leaders pledge to make participation in our

community a harassment-free experience for everyone, regardless of age, body

size, visible or invisible disability, ethnicity, sex characteristics, gender

identity and expression, level of experience, education, socio-economic status,

nationality, personal appearance, race, caste, color, religion, or sexual

identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,

diverse, inclusive, and healthy community.

Examples of behavior that contributes to a positive environment for our

community include:

* Demonstrating empathy and kindness toward other people

* Being respectful of differing opinions, viewpoints, and experiences

* Giving and gracefully accepting constructive feedback

* Accepting responsibility and apologizing to those affected by our mistakes,

and learning from the experience

* Focusing on what is best not just for us as individuals, but for the overall

community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of

any kind

* Trolling, insulting or derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or email address,

without their explicit permission

* Other conduct which could reasonably be considered inappropriate in a

professional setting

Community leaders are responsible for clarifying and enforcing our standards of

acceptable behavior and will take appropriate and fair corrective action in

response to any behavior that they deem inappropriate, threatening, offensive,

or harmful.

Community leaders have the right and responsibility to remove, edit, or reject

comments, commits, code, wiki edits, issues, and other contributions that are

not aligned to this Code of Conduct, and will communicate reasons for moderation

decisions when appropriate.

This Code of Conduct applies within all community spaces, and also applies when

an individual is officially representing the community in public spaces.

Examples of representing our community include using an official e-mail address,

posting via an official social media account, or acting as an appointed

representative at an online or offline event.

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported to the community leaders responsible for enforcement at codeofconduct@posit.co.

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the

reporter of any incident.

Community leaders will follow these Community Impact Guidelines in determining

the consequences for any action they deem in violation of this Code of Conduct:

**Community Impact**: Use of inappropriate language or other behavior deemed

unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing

clarity around the nature of the violation and an explanation of why the

behavior was inappropriate. A public apology may be requested.

**Community Impact**: A violation through a single incident or series of

actions.

**Consequence**: A warning with consequences for continued behavior. No

interaction with the people involved, including unsolicited interaction with

those enforcing the Code of Conduct, for a specified period of time. This

includes avoiding interactions in community spaces as well as external channels

like social media. Violating these terms may lead to a temporary or permanent

ban.

**Community Impact**: A serious violation of community standards, including

sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public

communication with the community for a specified period of time. No public or

private interaction with the people involved, including unsolicited interaction

with those enforcing the Code of Conduct, is allowed during this period.

Violating these terms may lead to a permanent ban.

**Community Impact**: Demonstrating a pattern of violation of community

standards, including sustained inappropriate behavior, harassment of an

individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the

community.

This Code of Conduct is adapted from the [Contributor Covenant][homepage],

version 2.1, available at

<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.

Community Impact Guidelines were inspired by

[Mozilla's code of conduct enforcement ladder][https://github.com/mozilla/inclusion].

For answers to common questions about this code of conduct, see the FAQ at

<https://www.contributor-covenant.org/faq>. Translations are available at <https://www.contributor-covenant.org/translations>.

[homepage]: https://www.contributor-covenant.org

name: R-CMD-check.yaml

permissions: read-all

- {os: macos-latest, r: 'release'}

# use 4.0 or 4.1 to check with rtools40's older compiler

- {os: windows-latest, r: 'oldrel-4'}

- {os: ubuntu-latest, r: 'devel', http-user-agent: 'release'}

- {os: ubuntu-latest, r: 'release'}

- {os: ubuntu-latest, r: 'oldrel-1'}

- {os: ubuntu-latest, r: 'oldrel-2'}

- {os: ubuntu-latest, r: 'oldrel-3'}

- {os: ubuntu-latest, r: 'oldrel-4'}

- uses: actions/checkout@v4

build_args: 'c("--no-manual","--compact-vignettes=gs+qpdf")'

on:

# Using `pull_request_target` over `pull_request` for elevated `GITHUB_TOKEN`

# privileges, otherwise we can't set `pull-requests: write` when the pull

# request comes from a fork, which is our main use case (external contributors).

#

# `pull_request_target` runs in the context of the target branch (`main`, usually),

# rather than in the context of the pull request like `pull_request` does. Due

# to this, we must explicitly checkout `ref: ${{ github.event.pull_request.head.sha }}`.

# This is typically frowned upon by GitHub, as it exposes you to potentially running

# untrusted code in a context where you have elevated privileges, but they explicitly

# call out the use case of reformatting and committing back / commenting on the PR

# as a situation that should be safe (because we aren't actually running the untrusted

# code, we are just treating it as passive data).

# https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/

pull_request_target:

name: format-suggest.yaml

jobs:

format-suggest:

name: format-suggest

runs-on: ubuntu-latest

permissions:

# Required to push suggestion comments to the PR

pull-requests: write

steps:

- uses: actions/checkout@v4

with:

ref: ${{ github.event.pull_request.head.sha }}

- name: Install

uses: posit-dev/setup-air@v1

- name: Format

run: air format .

- name: Suggest

uses: reviewdog/action-suggester@v1

with:

level: error

fail_level: error

tool_name: air

name: pkgdown.yaml

permissions: read-all

permissions:

contents: write

- uses: actions/checkout@v4

uses: JamesIves/github-pages-deploy-action@v4.5.0

name: test-coverage.yaml

permissions: read-all

- uses: actions/checkout@v4

extra-packages: any::covr, any::xml2

run: |

- uses: codecov/codecov-action@v5

with:

# Fail if error if not on PR, or if on PR and token is given

fail_ci_if_error: ${{ github.event_name != 'pull_request' || secrets.CODECOV_TOKEN }}

files: ./cobertura.xml

plugins: noop

disable_search: true

token: ${{ secrets.CODECOV_TOKEN }}

- name: Show testthat output

if: always()

run: |

shell: bash

- name: Upload test results

if: failure()

uses: actions/upload-artifact@v4

with:

name: coverage-test-failures

path: ${{ runner.temp }}/package

{

"recommendations": [

"Posit.air-vscode"

]

}

{

"[r]": {

"editor.formatOnSave": true,

"editor.defaultFormatter": "Posit.air-vscode"

},

"[quarto]": {

"editor.formatOnSave": true,

"editor.defaultFormatter": "quarto.quarto"

}

}