Contributions are welcome and greatly appreciated!
- Ensure that the bug was not already reported by searching in GitHub under Issues and the Cloudinary Support forms.
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
- If you require assistance in the implementation of cloudinary_gem please submit a request in the Cloudinary web site.
We would love to hear your requests! Please be aware that the GEM is used in a wide variety of environments and that some features may not be applicable to all users.
- Open a GitHub issue describing the benefits (and possible drawbacks) of the requested feature
- Follow the instructions detailed in Code contribution
- Open a new GitHub pull request
- Ensure the PR description clearly describes the bug / feature. Include the relevant issue number if applicable.
- Provide test code that covers the new code
- Make sure that your code works both with and without Rails
- The code should support:
- Ruby >= 1.8
- Rails >= 3.0
When contributing code, either to fix a bug or to implement a new feature, please follow these guidelines:
Fork project on Github and check out your copy.
git clone https://github.com/contributor/cloudinary_gem.git
cd cloudinary_gem
git remote add upstream https://github.com/cloudinary/cloudinary_gem.git
gem install bundler
bundle install
You can obtain the configuration URL from https://cloudinary.com/console.
export CLOUDINARY_URL=cloudinary://<api_key>:<api_secret>@<cloud>
bundle exec rspec -f d
Make sure your fork is up-to-date and create a topic branch for your feature or bug fix.
git checkout master
git pull upstream master
git checkout -b my-feature-branch
If you've been working on a change for a while, rebase with upstream/master.
git fetch upstream
git rebase upstream/master
git push origin my-feature-branch -f
Try to write a test that reproduces the problem you're trying to fix or describes a feature that you want to build. Add to test.
We definitely appreciate pull requests that highlight or reproduce a problem, even without a fix.
Implement your feature or bug fix. Follow the following style guide. Make sure that your code works both with and without Rails The code should support:
- Ruby >= 1.8
- Rails >= 3.0
Make sure that bundle exec rake test completes without errors.
Document any external behavior in the README.
Make sure git knows your name and email address:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
Writing good commit logs is important. A commit log should describe what changed and why.
git add ...
git commit
Please squash your commits into a single commit when appropriate. This simplifies future cherry picks and keeps the git log clean.
git push origin my-feature-branch
Go to https://github.com/contributor/cloudinary_gem and select your feature branch. Click the 'Pull Request' button and fill out the form. Pull requests are usually reviewed within a few days. Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
If you've been working on a change for a while, rebase with upstream/master.
git fetch upstream
git rebase upstream/master
git push origin my-feature-branch -f
Go back to your pull request after a few minutes and see whether it passed muster with Travis-CI. Everything should look green, otherwise fix issues and amend your commit as described above.
It's likely that your change will not be merged and that the nitpicky maintainers will ask you to do more, or fix seemingly benign problems. Hang on there!
Please do know that we really appreciate and value your time and work. We love you, really.