# Description ## Checklist: Fixing typos/Doc change - [ ] Each commit follows the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/#summary) format: e.g. `chore(readme): fixed typo`. See the end of this file for more information. ## Checklist: Bug Fix - [ ] Each commit follows the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/#summary) format: e.g. `chore(readme): fixed typo`. See the end of this file for more information. - [ ] All existing unit tests are still passing (if applicable) - [ ] Add new passing unit tests to cover the code introduced by your PR - [ ] Update the readme - [ ] Update or add any necessary API documentation - [ ] Add some [steps](#steps-to-test) so we can test your bug fix ## Checklist: New Feature - [ ] Each commit follows the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/#summary) format: e.g. `chore(readme): fixed typo`. See the end of this file for more information. - [ ] Any breaking changes are specified on the commit on which they are introduced with `BREAKING CHANGE` in the body of the commit. - [ ] If this is a big feature with breaking changes, consider [opening an issue](https://github.com/imgix/imgix-rb/issues/new?labels=&template=feature_request.md&title=) to discuss first. This is completely up to you, but please keep in mind that your PR might not be accepted. - [ ] Run unit tests to ensure all existing tests are still passing - [ ] Add new passing unit tests to cover the code introduced by your PR - [ ] Update the readme - [ ] Add some [steps](#steps-to-test) so we can test your cool new feature! ## Steps to Test Related issue: [e.g. #42] Code: ```rb // A standalone Ruby example of what the PR solves ```