First off, thanks for taking the time to contribute! ❤️
All types of contributions are encouraged and valued. Here, we collected some advice to smooth out the experience for everyone involved.
Table of content
And if you like the project, but just don't have time to contribute, that's fine. Publicity in the form of github star, a tweet, mentioning in your project's readme and/or telling a friend (at a meetup) help as well.
Some questions can be answered by reading our documentation including the FAQ page.
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue.
If you then still feel the need to ask a question and need clarification, we recommend the following:
Head over to our issue page and file an issue.
Please search also the closed issues whether your question has been answered before.
Legal Notice
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
Contributing follows mostly the following steps:
- For bigger changes, open an issue and/or drop by on our discord so that we can coordinate.
- Fork the repository
- Create a new branch
- Apply your changes
- Add/Adapt tests as necessary
- Run the tests
- Run tests locally via
./gradlew test
(includesunitTest
andintegrationTest
targets, which executes faster)
- Run tests locally via
- Run the code formatter
- We use the palantir code style and disallow wildcard imports
- Run
./gradlew spotlessApply
to fix most things automatically
- Commit your changes & push
- Open a Pull-Request against the springwolf repository
- Use the provided template to briefly describe why the changes should be included
- Update the documentation as necessary
- Add yourself to the contributors and your company to the users in README.md