Merge branch 'main' into check_smooth

.Rbuildignore

@@ -8,16 +8,21 @@
 
 ^\.travis.yml
 ^\_pkgdown.yml
+^\_pkgdown.yaml
+^paper.bib$
 
 ^data/.
 ^docs/.
 ^vignettes/.
 ^pkgdown/.
 ^WIP/.
-^paper/.
+^papers/.
 ^.github/.
 ^CODE_OF_CONDUCT\.md$
 ^revdep$
 ^tests/_snaps/.
 ^cran-comments\.md$
 ^\.github$
+\.code-workspace$
+\.lintr$
+^CRAN-SUBMISSION$

.github/SUPPORT.md

@@ -0,0 +1,29 @@
+# Getting help with `{performance}`
+
+Thanks for using `{performance}`. Before filing an issue, there are a few places
+to explore and pieces to put together to make the process as smooth as possible.
+
+Start by making a minimal **repr**oducible **ex**ample using the
+[reprex](http://reprex.tidyverse.org/) package. If you haven't heard of or used
+reprex before, you're in for a treat! Seriously, reprex will make all of your
+R-question-asking endeavors easier (which is a pretty insane ROI for the five to
+ten minutes it'll take you to learn what it's all about). For additional reprex
+pointers, check out the [Get help!](https://www.tidyverse.org/help/) resource
+used by the tidyverse team.
+
+Armed with your reprex, the next step is to figure out where to ask:
+
+  * If it's a question: start with StackOverflow. There are more people there to answer questions.
+  * If it's a bug: you're in the right place, file an issue.
+  * If you're not sure: let's [discuss](https://github.com/easystats/performance/discussions) it and try to figure it out! If your
+    problem _is_ a bug or a feature request, you can easily return here and
+    report it.
+
+Before opening a new issue, be sure to [search issues and pull requests](https://github.com/easystats/performance/issues) to make sure the
+bug hasn't been reported and/or already fixed in the development version. By
+default, the search will be pre-populated with `is:issue is:open`. You can
+[edit the qualifiers](https://help.github.com/articles/searching-issues-and-pull-requests/)
+(e.g. `is:pr`, `is:closed`) as needed. For example, you'd simply
+remove `is:open` to search _all_ issues in the repo, open or closed.
+
+Thanks for your help!

.github/dependabot.yaml

@@ -0,0 +1,8 @@
+version: 2
+
+updates:
+  # Keep dependencies for GitHub Actions up-to-date
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/R-CMD-check-devel-easystats.yaml

@@ -0,0 +1,11 @@
+on:
+  schedule:
+    # * is a special character in YAML so you have to quote this string
+    # Trigger once a week at 00:00 on Sunday
+    - cron: "0 0 * * SUN"
+
+name: R-CMD-check-devel-easystats
+
+jobs:
+  R-CMD-check-devel-easystats:
+    uses: easystats/workflows/.github/workflows/R-CMD-check-devel-easystats.yaml@main

.github/workflows/R-CMD-check-hard.yaml

@@ -0,0 +1,19 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+#
+# NOTE: This workflow only directly installs "hard" dependencies, i.e. Depends,
+# Imports, and LinkingTo dependencies. Notably, Suggests dependencies are never
+# installed, with the exception of testthat, knitr, and rmarkdown. The cache is
+# never used to avoid accidentally restoring a cache containing a suggested
+# dependency.
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: R-CMD-check-hard
+
+jobs:
+  R-CMD-check-hard:
+    uses: easystats/workflows/.github/workflows/R-CMD-check-hard.yaml@main

.github/workflows/R-CMD-check-strict.yaml

@@ -0,0 +1,15 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+#
+# R CMD Check will fail on a `NOTE`.
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: R-CMD-check-strict
+
+jobs:
+  R-CMD-check-strict:
+    uses: easystats/workflows/.github/workflows/R-CMD-check-strict.yaml@main

.github/workflows/R-CMD-check.yaml

@@ -0,0 +1,17 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+#
+# NOTE: This workflow is overkill for most R packages and
+# check-standard.yaml is likely a better choice.
+# usethis::use_github_action("check-standard") will install it.
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: R-CMD-check
+
+jobs:
+  R-CMD-check:
+    uses: easystats/workflows/.github/workflows/R-CMD-check.yaml@main

.github/workflows/check-all-examples.yaml

@@ -0,0 +1,19 @@
+# Make sure all examples run successfully, even the ones that are not supposed
+# to be run or tested on CRAN machines by default.
+#
+# The examples that fail should use
+#  - `if (FALSE) { ... }` (if example is included only for illustrative purposes)
+#  - `try({ ... })` (if the intent is to show the error)
+#
+# This workflow helps find such failing examples that need to be modified.
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-all-examples
+
+jobs:
+  check-all-examples:
+    uses: easystats/workflows/.github/workflows/check-all-examples.yaml@main

.github/workflows/check-link-rot.yaml

@@ -0,0 +1,11 @@
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-link-rot
+
+jobs:
+  check-link-rot:
+    uses: easystats/workflows/.github/workflows/check-link-rot.yaml@main

.github/workflows/check-random-test-order.yaml

@@ -0,0 +1,12 @@
+# Run tests in random order
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-random-test-order
+
+jobs:
+  check-random-test-order:
+    uses: easystats/workflows/.github/workflows/check-random-test-order.yaml@main

.github/workflows/check-readme.yaml

@@ -0,0 +1,14 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-readme
+
+jobs:
+  check-readme:
+    uses: easystats/workflows/.github/workflows/check-readme.yaml@main

.github/workflows/check-spelling.yaml

@@ -0,0 +1,11 @@
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-spelling
+
+jobs:
+  check-spelling:
+    uses: easystats/workflows/.github/workflows/check-spelling.yaml@main

.github/workflows/check-styling.yaml

@@ -0,0 +1,11 @@
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-styling
+
+jobs:
+  check-styling:
+    uses: easystats/workflows/.github/workflows/check-styling.yaml@main

.github/workflows/check-test-warnings.yaml

@@ -0,0 +1,12 @@
+# Running tests with options(warn = 2) to fail on test warnings
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-test-warnings
+
+jobs:
+  check-test-warnings:
+    uses: easystats/workflows/.github/workflows/check-test-warnings.yaml@main

.github/workflows/check-vignette-warnings.yaml

@@ -0,0 +1,12 @@
+# Running tests with options(warn = 2) to fail on test warnings
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: check-vignette-warnings
+
+jobs:
+  check-vignette-warnings:
+    uses: easystats/workflows/.github/workflows/check-vignette-warnings.yaml@main

.github/workflows/html-5-check.yaml

@@ -0,0 +1,13 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: HTML5 check
+
+jobs:
+  HTML5-check:
+    uses: easystats/workflows/.github/workflows/html-5-check.yaml@main

.github/workflows/lint-changed-files.yaml

@@ -0,0 +1,11 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+on:
+  pull_request:
+    branches: [main, master]
+
+name: lint-changed-files
+
+jobs:
+  lint-changed-files:
+    uses: easystats/workflows/.github/workflows/lint-changed-files.yaml@main

.github/workflows/lint.yaml

@@ -0,0 +1,13 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: lint
+
+jobs:
+  lint:
+    uses: easystats/workflows/.github/workflows/lint.yaml@main

.github/workflows/pkgdown-no-suggests.yaml

@@ -0,0 +1,11 @@
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+
+name: pkgdown-no-suggests
+
+jobs:
+  pkgdown-no-suggests:
+    uses: easystats/workflows/.github/workflows/pkgdown-no-suggests.yaml@main

.github/workflows/pkgdown.yaml

@@ -0,0 +1,16 @@
+# Workflow derived from https://github.com/r-lib/actions/tree/v2/examples
+# Need help debugging build failures? Start at https://github.com/r-lib/actions#where-to-find-help
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+    branches: [main, master]
+  release:
+    types: [published]
+  workflow_dispatch:
+
+name: pkgdown
+
+jobs:
+  pkgdown:
+    uses: easystats/workflows/.github/workflows/pkgdown.yaml@main