From 51be1abd4920770cae53f3cd1eb7a57d38d52e71 Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 9 Jan 2025 12:17:08 +0100 Subject: [PATCH] fix link --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index ec9208fb0..4163994ba 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,6 +1,6 @@ # Contributing to insight -This outlines how to propose a change to **insight**. +This outlines how to propose a change to **insight**. ## Fixing typos @@ -16,7 +16,7 @@ bug, you may also create an associated issue. If possible, try to illustrate you * Please create a Git branch for each pull request (PR). * Your contributed code should roughly follow the [R style guide](http://style.tidyverse.org), but in particular our [**easystats convention of code-style**](https://github.com/easystats/easystats#convention-of-code-style). * insight uses [roxygen2](https://cran.r-project.org/package=roxygen2), with -[Markdown syntax](https://cran.r-project.org/web/packages/roxygen2/vignettes/markdown.html), +markdown syntax, for documentation. * insight uses [testthat](https://cran.r-project.org/package=testthat). Adding tests to the PR makes it easier for me to merge your PR into the code base. * If your PR is a user-visible change, you may add a bullet to the top of `NEWS.md` describing the changes made. You may optionally add your GitHub username, and links to relevant issue(s)/PR(s).