RhodeCode / docs / contributing.rst

Contributing to RhodeCode

If you would like to contribute to RhodeCode, please contact me, any help is greatly appreciated!

Could I request that you make your source contributions by first forking the RhodeCode repository on bitbucket https://bitbucket.org/marcinkuzminski/rhodecode and then make your changes to your forked repository. Please post all fixes into BETA branch since your fix might be already fixed there and i try to merge all fixes from beta into stable, and not the other way. Finally, when you are finished making a change, please send me a pull request.

To run RhodeCode in a development version you always need to install the latest required libs from requires.txt file.

after downloading/pulling RhodeCode make sure you run:

python setup.py develop

command to install/verify all required packages, and prepare development enviroment.

After finishing your changes make sure all tests passes ok. You can run the testsuite running nosetest from the project root.

Thank you for any contributions!
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.