You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This outlines how to propose a change to {carver}.
4
+
5
+
## Making Changes
6
+
7
+
If you want to make a change, it's a good idea to first file an issue and make sure someone from the team agrees that it’s needed.
8
+
Per pfizer-opensource policies, only those listed as collaborators can raise issues.
9
+
If you’ve found a bug, please email the maintainer (`smriti.anand@pfizer.com`) illustrating the bug with a minimal
10
+
[reprex](https://www.tidyverse.org/help/#reprex) (this will also help you write a unit test, if needed).
11
+
Alternatively if you have access to the COSA community Slack channel for {carver}, you can raise it there.
12
+
See guide on [how to create a great issue](https://code-review.tidyverse.org/issues/) for more advice.
13
+
14
+
### Pull request process
15
+
16
+
* Fork the package and clone onto your computer.
17
+
18
+
* If needed, install all development dependencies with `devtools::install_dev_deps()`, and then make sure the package passes R CMD check by running `devtools::check()`.
19
+
If R CMD check doesn't pass cleanly, it's a good idea to ask for help before continuing.
20
+
* Create a Git branch for your pull request (PR).
21
+
22
+
* Make your changes, commit to git, and then create a PR.
23
+
The title of your PR should briefly describe the change.
24
+
The body of your PR should contain `Closes #issue-number`.
25
+
26
+
* For user-facing changes, add a bullet to the top of `NEWS.md` (i.e. just below the first header). Follow the style described in <https://style.tidyverse.org/news.html>.
27
+
28
+
### Code Style
29
+
30
+
* New code should follow the tidyverse [style guide](https://style.tidyverse.org).
31
+
You can use the [styler](https://CRAN.R-project.org/package=styler) package to apply these styles, but please don't restyle code that has nothing to do with your PR.
32
+
33
+
* To apply the appropriate style with styler please use `styler:::style_active_pkg()` or `styler::style_file()`
34
+
35
+
* We use [roxygen2](https://cran.r-project.org/package=roxygen2), with [Markdown syntax](https://cran.r-project.org/web/packages/roxygen2/vignettes/rd-formatting.html), for documentation.
36
+
37
+
* We use [testthat](https://cran.r-project.org/package=testthat) for unit tests.
38
+
Contributions with test cases included are easier to accept.
39
+
40
+
* All helper/non-exported functions are documented with roxygen2 as indicated above.
41
+
Include `#' @keywords internal` to mark the function as internal.
42
+
Any helper functions that appear in examples will need to use the `carver:::`
43
+
prefix.
44
+
45
+
### Error Handling
46
+
47
+
TBD
48
+
49
+
### Package Dependencies
50
+
51
+
Additional package dependencies should be considered after exhausting other possibilities. If you do need to add one,
52
+
email the maintainer or collaborators/start a discussion to make a decision on the necessity of it.
53
+
Once agreed upon, the dependency can be added to the package via the relevant files.
54
+
55
+
## Scope
56
+
57
+
The {carver} package will be an open-source tool and package to enable generation of
58
+
common analysis reports (tables and interactive plots) for clinical
59
+
review and direct inclusion in submission for regulatory agencies
60
+
61
+
## Deprecation Cycle
62
+
63
+
TBD
64
+
65
+
## Code of Conduct
66
+
67
+
Please note that the carver project is released with a
68
+
[Contributor Code of Conduct](CODE_OF_CONDUCT.md). By contributing to this
0 commit comments