Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add essential GitHub Actions for ensuring package health

Open Beginner friendly
  • Is something wrong?
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, r
Domain
ci-cd, testing

Research direction

Start with the existing test suite and the GitHub Actions guidance linked in the issue, including the R packages book and r-lib/actions templates. Add workflows for test coverage, R CMD check, and linting, using usethis templates where helpful. Done means these checks run through GitHub Actions when code changes and complete successfully.

Written by the indexing model from the issue text.

Description

Wrt to the JOSS review at https://github.com/openjournals/joss-reviews/issues/11373, your package is currently missing essential GitHub Actions for continuous integration and package health, including:

  • test-coverage: You have a test suite but no GitHub Actions workflow to re-run them when the code changes. This could lead to a lot of bugs, being introduced into the code. See the R packages book for guidance.
  • R cmd check: to ensure the package is being built continuously without errors
  • Linting: These ensure the codeabase is using high standards of R software engineering

For motivation for doing this, see the continuous integration section of the R packages v2 book.

A lot of these can be quickly added using the usethis R package with a lot of templates from R lib.

Please let me know if you need help proceeding with this as I feel strongly about it.

Dominant language
R
Stars
2
Forks
3
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CDCgov/nbbp

All issues in CDCgov/nbbp

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.