Tools to monitor the health of your CRAN packages
Open
Nobody has claimed this yet.
best-practice
cran
r-package
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
This blog post discusses how to monitor the health of your CRAN packages. The CRAN checks API and cchecks R package can help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked blog post, CRAN checks API, and cchecks R package to determine the intended resource entry and where resources are maintained. Done should be a clear, accurate addition describing these monitoring tools, but the issue does not name a file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100