How we write code at Feedcast
- Star the project.
- Open or find an issue here.
- Fork it (https://github.com/feedcast/core/fork)
- Create your feature branch (git checkout -b my-awesome-new-feature)
- Commit your changes (follwing our commit policy and style guide)
- Push to the branch (git push origin my-new-feature)
- Create a new Pull Request
Currently, we are using Thoughtbot's Style Guide for Ruby Code.
We have a very rigid commit policy, to contribute please follow these rules:
feature: Add hat wobble
^--^ ^------------^
| |
| +-> Summary in present tense
|
+-------> Type: chore, doc, feature, fix, refactor, style, or test
- chore: Add oyster build script
- doc: Explain hat wobble
- feature: Add beta sequence
- fix: Remove broken confirmation message
- refactor: Share logic between 4d3d3d3 and flarhgunnstow
- style: Convert tabs to spaces
- test: Ensure Tayne retains clothing
Based on this.