This is an automated email from the ASF dual-hosted git repository.
rfscholte pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 3648afc Update guide-maven-development.apt
3648afc is described below
commit 3648afceb86b0f3c9a190ccdd1f6466d00e621f1
Author: Robert Scholte <rfscho...@apache.org>
AuthorDate: Sun Jan 16 12:04:05 2022 +0100
Update guide-maven-development.apt
---
content/apt/guides/development/guide-maven-development.apt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/apt/guides/development/guide-maven-development.apt
b/content/apt/guides/development/guide-maven-development.apt
index 344ba55..a39eee1 100644
--- a/content/apt/guides/development/guide-maven-development.apt
+++ b/content/apt/guides/development/guide-maven-development.apt
@@ -75,6 +75,10 @@ Developing Maven
The most convenient way is to create a GitHub fork from the Git repository
you are working with.
When you have either completed an issue or just want some feedback on the
work you have done, create a pull request.
We have a couple of guidelines when submitting contributions:
+
+ * Verify the status of the <<<master>>> branch on
{{{https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-master-jobs.html}Maven
CI}}.
+ If it is not SUCCCESS, then first try to figure out the problem, don't
start with your own issue yet! You can use <<<git bisect>>> to figure out the
problematic commit and help
+ with that committer to solve the problem.
* Create your branch from <<<master>>>, not from a tag. Otherwise, your patch
is outdated the moment you create it and might not be applicable
to the development head.
