- Code of Conduct
- Contributor License Agreement
- Code Organization
- Setting Up the project locally
- Local Development for Desktop
- Submitting a Pull Request
- Add yourself as a contributor
We have a code of conduct you can find here and every contributor is expected to obey the rules therein. Any issues or PRs that don't abide by the code of conduct may be closed.
Check out the overview in readme for the structure of the project.
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub
To install the project you need to have node
and npm
installed
-
Fork the project, clone your fork:
# Clone your fork git clone https://github.com/<your-username>/our-garden.git # Navigate to the newly cloned directory cd our-garden
-
from the root of the project:
npm install
all dependencies- make sure you have latest
npm
version
- make sure you have latest
-
from the root of the project:
npm start
Tip: Keep your
master
branch pointing at the original repository and make pull requests from branches on your fork. To do this, run:git remote add upstream https://github.com/community-garden/our-garden git fetch upstream git branch --set-upstream-to=upstream/master masterThis will add the original repository as a "remote" called "upstream," then fetch the git information from that remote, then set your local
master
branch to use the upstream master branch whenever you rungit pull
. Then you can make all of your pull request branches based on thismaster
branch. Whenever you want to update your version ofmaster
, do a regulargit pull
.
Our-Garden App can be built and developed on a host machine running a recent version of node
, which can be managed bynvm
. See individual instructions for your OS on how to install the
node version manager. Either a local running neo4j database must be present or you can use our supplied
docker-compose.yml
setup. By running npm run docker:up
you will have all dependant services
at a glance.
$ npm run start
Please go through existing issues and pull requests to check if somebody else is
already working on it, we use someone working on it
label to mark such issues.
husky
will run type checking, prettier and a linter before you are allowed to commit
but you may run these commands seperately
npm test
npm run lint
npm run format
This project follows the all-contributors specification. Contributions of any kind welcome!