|author||dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>||Mon Sep 06 09:17:56 2021 +0000|
|committer||Sylwester Lachiewicz <email@example.com>||Mon Sep 06 13:22:25 2021 +0200|
Bump maven-verifier from 1.6 to 1.7.2 Bumps [maven-verifier](https://github.com/apache/maven-verifier) from 1.6 to 1.7.2. - [Release notes](https://github.com/apache/maven-verifier/releases) - [Commits](https://github.com/apache/maven-verifier/compare/maven-verifier-1.6...maven-verifier-1.7.2) --- updated-dependencies: - dependency-name: org.apache.maven.shared:maven-verifier dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <firstname.lastname@example.org>
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
git diff --checkbefore committing.
[MEAR-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verifyto assure nothing else was accidentally broken.
If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.