From 6c915a9f089be56a8419c7f1e2f1303abd35746c Mon Sep 17 00:00:00 2001 From: Michael Chirico Date: Sun, 1 Dec 2024 22:30:53 -0800 Subject: [PATCH] tweak --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index b5d9e6b1f..10289cd35 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -24,7 +24,7 @@ If you wish to contribute a new linter, the [Creating new linters](https://lintr * Make your changes, commit them to Git, and create a PR using `usethis::pr_push()`. Follow the prompts in your browser to complete the process. Use a concise title for your PR that summarizes the change, and include `Fixes #issue-number` in the PR _description_. Doing so will automatically close the linked issue when the PR is merged. For complicated changes, add a textual overview of what your PR does in the description. Consider breaking up large PRs into a chain of more digestible+focused smaller PRs. -* For user-facing changes, add a bullet appropriately in the top section of `NEWS.md` (i.e. below the first header). Follow the style described in . Your audience for NEWS items is a package user, i.e., _not_ a package developer. +* For user-facing changes, add a bullet appropriately in the top section of `NEWS.md` (i.e. below the first header). Follow the style described in . Most importantly, your audience for NEWS items is a package user, i.e., _not_ a package developer. ### Code style