We'd love to get patches from you!
mvn clean verify
We follow the GitHub Flow Workflow
- Fork the project
- Check out the
main
branch - Create a feature branch
- Write code and tests for your change
- From your branch, make a pull request against
https://github.com/spotify/fmt-maven-plugin/main
- Work with repo maintainers to get your change reviewed
- Wait for your change to be pulled into
https://github.com/spotify/fmt-maven-plugin/main
- Delete your feature branch
Change the version with mvn versions:set -DnewVersion=x.y.z-SNAPSHOT
, do a mvn install
and then use x.y.z-SNAPSHOT
as the new plugin version in your other Maven project (or this project).
Quite obviously this project uses the google-java-format
When creating an issue please try to adhere to the following format:
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior.
Expected behavior A clear and concise description of what you expected to happen.
Additional context Add any other context about the problem here.
Before opening a pull request, make sure mvn verify
runs successfully, this will also format your code with this plugin.
If there is already a GitHub issue for the task you are working on, leave a comment to let people know that you are working on it. If there isn't already an issue and it is a non-trivial task, it's a good idea to create one (and note that you're working on it). This prevents contributors from duplicating effort.
Branch protection is set up to require one approving review from maintainers of this repo.
See README
We also welcome improvements to the project documentation or to the existing docs. Please file an issue.
By contributing your code, you agree to license your contribution under the terms of the LICENSE
Read our Code of Conduct for the project.