-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,25 +17,25 @@ Contribute | |
To contribute you can follow these steps | ||
|
||
|
||
1. Install the current version of *R*, and *git*. You can also install *R-Studio*. | ||
2. **install** `R` package "carobiner" with ``remotes::install_github("reagro/carobiner")`` | ||
1. **Install** the current version of `R <https://cran.r-project.org/>`__ and `git <https://git-scm.com/downloads>`__. You can also install `R-Studio <https://posit.co/download/rstudio-desktop/>`__. | ||
2. In *R*, **install** the "carobiner" package with ``remotes::install_github("reagro/carobiner")`` (you may need to first run ``install.packages("remotes")``). | ||
3. **fork** the *Carob* `repo <https://github.com/reagro/carob/>`_ to your github account. | ||
4. **clone** the forked repo to your computer. | ||
5. create a new `R` **script**, or make the changes to an existing script. See this `example <./example.html>`__ and the `guidelines <https://github.com/reagro/carob/wiki/Guidelines>`_). | ||
5. create a new `R` **script**, or make the changes to an existing script. See this `example <./example.html>`__ and the `guidelines <https://github.com/reagro/carob/wiki/Guidelines>`_. | ||
6. **check** your work by running ``carobiner::run_carob()`` for the new or changed `R` script. | ||
7. **sync** the forked repo with main repo in reagro/carob such that your fork is not behind. | ||
8. **add** and/or **commit** these changes to the forked repo on your github account. | ||
9. **push** your changes to the forked repo on your github account. | ||
10. create a **pull request** to integrate your changes into the main repo. Keep pull requests simple. They should normally consist of only one file at a time. | ||
|
||
If you are not familiar with these procedures you can try to follow `these <./github.html>`__ instructions | ||
If you are not familiar with these procedures you can try to follow `these instructions <./github.html>`__. | ||
|
||
If you find this procedure too daunting we can also try to work with you in other ways. You can drop us an email at [email protected], or raise an `issue <https://github.com/reagro/carob/issues>`_ on github. | ||
|
||
You can discover new data sets with the `Gardian <https://gardian.bigdata.cgiar.org>`_ search engine. You can also look at our to-do list below for ideas. You can check our `done list <done.html>`_ to make sure you do not work on a dataset that has already been processed). But since there can be a delay in updating what is shown here, before you start working on a dataset, you should check with ``carobiner::on_github`` if it has already been done (and has been added to the github repo). | ||
|
||
.. raw:: html | ||
:file: _R/todo.html | ||
:file: ../_R/todo.html | ||
|
||
|
||
.. raw:: html | ||
|