• Do not open up a GitHub issue if the bug is a security vulnerability in Spring Cloud AWS, and instead to refer to our security policy.

• Ensure the bug was not already reported by searching on GitHub under Issues.

• 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, ideally with a code sample or an executable test case demonstrating the expected behavior that is not occurring.

• Open a new GitHub pull request with the patch.

• Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

• Suggest your change in the Issues.

• Start writing code once the issue got approved by project maintainers.

• In addition to actual implemented feature, remember to:

  • update reference docs
  • consider providing/updating one of the sample applications
  • each public class should have a Javadoc
  • code has to have tests
  • each package has to have package-info.java file definining nullability rules (example)
  • each nullable field, method parameter, method return value, if can be null, has to be annotated with org.springframework.lang.Nullable.

• Ask any question about how to use Spring Cloud AWS in the Discussions.

To avoid setting up your local development environment, you can use Gitpod and develop directly in browser based Visual Studio Code, or JetBrains Client via JetBrains Gateway.

Note: The above button does not work on Privacy oriented browsers, please click here to open the project on gitpod.

Thanks!