Sha256: 77bcb90e3e15c0497b4172d378e0cc54b1f8c10283dba660c4cb190664b68f3c
Contents?: true
Size: 1.32 KB
Versions: 3
Compression:
Stored size: 1.32 KB
Contents
Changelog ========= ## Fork the project Fork the project on the [project page]( https://github.com/Antek-drzewiecki/wine_bouncer/fork ) Checkout the project from your own repository. ``` git clone https://github.com/[your github username]/wine_bouncer.git cd wine_bouncer git remote add upstream https://github.com/Antek-drzewiecki/wine_bouncer.git ``` ## Create your feature branch Make sure your fork is [up to date](https://help.github.com/articles/syncing-a-fork) and make a feature from the master branch. `git checkout -b my-new-feature` ## Prepare your development environment See [README](README.md#development) Run your specs to make sure nothing is broken ;) ## Write Tests and/or Code We appreciate pull requests. Even specs only to identify an problem! Because we want to ensure the quality of our gem. We cannot accept functional changes without tests. ## Write documentation Documentation is appreciated. Its nice to know people know how to use features. Also feel free to update the changelog with the changes. ## Commit your changes Commit your changes. `git add ...` `git commit -m 'Add some feature'` ## Push your changes Push to the branch. `git push origin my-new-feature` ## Create a pull request Check your feature branch, once its passes Travis-CI, create a pull request Thanks you for participating!
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
wine_bouncer-0.1.2 | CONTRIBUTING.md |
wine_bouncer-0.1.1 | CONTRIBUTING.md |
wine_bouncer-0.1.0 | CONTRIBUTING.md |