Skip to content
This repository has been archived by the owner on Feb 14, 2023. It is now read-only.

Latest commit

 

History

History
79 lines (62 loc) · 4.09 KB

CONTRIBUTING.md

File metadata and controls

79 lines (62 loc) · 4.09 KB
Raw

Issues

If you encounter an issue with the IBM Cloud Spring Boot support, you are welcome to submit a bug report. Before that, please search for similar issues. It's possible somebody has encountered this issue already.

Pull Requests

If you want to contribute to the repository, here's a quick guide:

  1. Fork the repository
  2. Develop and test your changes. * Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change. * Check for unnecessary whitespace with git diff --check before committing.
  3. Commit your changes:
    * Use the present tense ("Add feature" not "Added Feature") * Use the imperative mood ("Move cursor to…" not "Moves cursor to…") * Include relevant Emoji from our Emoji cheatsheet 😄
  4. Push to your fork and submit a pull request to the master branch

Testing

To test/run your changes locally:

  1. Make your changes. Update the <version> in pom.xml to distinguish your version from any versions in the local Maven cache. Standard semantic versioning (major.minor.patch) conventions are used. Be sure to update/add tests for your changes.

  2. Build the project by issuing mvn package. Make sure the tests all pass.

  3. Install the dependency locally with the following command:

    mvn install:install-file -Dfile=target/ibm-cloud-spring-boot-service-bind-1.x.x.jar -DpomFile=pom.xml

  4. Include the dependency in another project and use as described in the Usage section in the README, substituting your version number (1.x.x in the above command).

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Emoji Cheatsheet

When creating creating commits or updating the CHANGELOG, please start the commit message or update with one of the following applicable Emoji. Emoji should not be used at the start of issue or pull request titles.

  • 🆕 :new: when adding new functionality
  • 🐛 :bug: when fixing a bug
  • 📝 :memo: when writing documentation
  • 🎨 :art: when improving the format/structure of the code
  • 🔥 :fire: when removing code or files
  • 🐎 :racehorse: when improving performance
  • ✅ :white_check_mark: when adding tests
  • 💚 :green_heart: when fixing the CI build
  • 🔒 :lock: when dealing with security
  • 🔮 :crystal_ball: when experimenting
  • 😒 :unamused: when doing chore work (updating dependencies, etc…)
  • 💥 :boom: when changing in a non-backwards-compatible way current functionality
  • :shipit: :shipit: when creating a new release

Additional Resources