mitchelloharawild / mitchelloharawild/graphvec
Release graphvec 0.1.0
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
First release:
-
usethis::use_cran_comments() - Update (aspirational) install instructions in README
- Proofread
Title:andDescription: - Check that all exported functions have
@returnand@examples - Check that
Authors@R:includes a copyright holder (role 'cph') - Check licensing of included files
- Review https://github.com/DavisVaughan/extrachecks
Prepare for release:
-
git pull -
urlchecker::url_check() -
devtools::build_readme() -
devtools::check(remote = TRUE, manual = TRUE) -
devtools::check_win_devel() -
git push - Draft blog post
Submit to CRAN:
-
usethis::use_version('minor') -
devtools::submit_cran() - Approve email
Wait for CRAN...
- Accepted 🎉
- Finish & publish blog post
- Add link to blog post in pkgdown news menu
-
usethis::use_github_release() -
usethis::use_dev_version(push = TRUE) - Share on social media
Contributor guide
No contributing guide indexed for this repository
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
Start with the remaining unchecked items in the issue, especially the usethis and devtools release commands, and review the README, pkgdown news menu, and draft blog post requirements. Confirm the CRAN submission and email approval steps, then track acceptance before completing the release, blog, news link, development-version, and announcement steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100