Contributing ------------ As an open source project, your contributions are important to the future of Cappuccino. Whether you're looking to write code, add new documentation, or just report a bug, you'll be helping everyone who uses Cappuccino in the future. ## Reporting Bugs We use [GitHub to track issues](https://github.com/cappuccino/cappuccino/issues). You might be interested in our [issue life cycle](http://www.cappuccino-project.org/community/contribute/the-issue-lifecycle/) which explains the process of how an issue is taken from new to resolved. ## Patches To contribute a patch or a fix, fork Cappuccino and then clone your fork and make the changes to a branch of your fork: git clone https://github.com//cappuccino.git git checkout -b descriptive-branch-name master # Check that the unit tests work. jake test # Make changes. Make sure you follow the coding style guidelines and write unit tests. # Check that everything is still working, then commit. jake test git commit git push origin descriptive-branch-name Now you can go to GitHub and [make a pull request](https://help.github.com/articles/using-pull-requests). Some things are difficult to unit test in a way that's worthwhile. For instance a change to the mouse interaction of a `CPButton`. In this case a manual test is fine instead. Find the closest related manual test in `Tests/Manual` and add whatever it takes to easily reproduce the patched behavior, ideally with some labels describing how someone running the manual test should exercise it. ## Commit Messages The style and format of your commit messages are very important to the health of the project. A good commit message helps not only users reading the release notes, but also your fellow Cappuccino developers as they review `git log` or `git blame` to figure out what you were doing. Commit messages should be in the following format: :