Add documentation about how to handle closely related packages
Open
@mpadge is already working on this.
Since Nov 22, 2022.
content :page_with_curl:
- Dominant language
- R
- Stars
- 164
- Forks
- 69
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 5
Description
Some packages are designed to work well together, or one package may not have any use at all without the other (e.g., {targets} and {tarchetypes}). There should be formal guidance on how to treat such packages during code review (under what circumstances should they be included in a single review vs. split, etc.)
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.
Assessment
This issue has not been assessed yet.