This is an automated email from the ASF dual-hosted git repository.

gnodet pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven.git


The following commit(s) were added to refs/heads/master by this push:
     new d97467698b Clarify Maven contributor testing workflow (#13753)
d97467698b is described below

commit d97467698bdd0d11ae551b05ada7396770778f7c
Author: codewithsinchana <[email protected]>
AuthorDate: Tue Nov 3 23:20:18 2026 +0530

    Clarify Maven contributor testing workflow (#13753)
    
    * Clarify Maven contributor testing workflow
    
    * Update contributor formatting instructions
    
    * Fix CONTRIBUTING.md trailing newline
    
    ---------
    
    Co-authored-by: codewithsinchana <[email protected]>
---
 CONTRIBUTING.md | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a5b2476665..4a352e9a0e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,19 +1,20 @@
-<!---
- Licensed to the Apache Software Foundation (ASF) under one or more
- contributor license agreements.  See the NOTICE file distributed with
- this work for additional information regarding copyright ownership.
- The ASF licenses this file to You under the Apache License, Version 2.0
- (the "License"); you may not use this file except in compliance with
- the License.  You may obtain a copy of the License at
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
 
-      http://www.apache.org/licenses/LICENSE-2.0
+     http://www.apache.org/licenses/LICENSE-2.0
 
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
 -->
+
 Contributing to Apache Maven
 ======================
 
@@ -43,19 +44,18 @@ Making and Submitting Changes
 --------------
 
 We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] 
is the
-main channel of communication for contributors.  
-There are some guidelines which will make applying PRs easier for us:
+main channel of communication for contributors. There are some guidelines which
+will make applying PRs easier for us:
+
 + Create a topic branch from where you want to base your work (this is usually 
the master branch).
   Push your changes to a topic branch in your fork of the repository.
 + Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
-  patches should only highlight the actual difference, not being disturbed by 
any formatting issues:
++ Respect the original code style by following the same 
[codestyle][code-style].
   + Only use spaces for indentation.
-  + Create minimal diffs - disable on save actions like reformat source code 
or organize imports.
-    If you feel the source code should be reformatted, create a separate PR 
for this change.
+  + Run `mvn spotless:apply` to apply the project's automatic formatting 
before submitting your changes.
   + Check for unnecessary whitespace with `git diff --check` before committing.
 + Make sure you have added the necessary tests (JUnit/[Core IT 
tests][core-it]) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was 
accidentally broken.
++ During development, run the relevant module tests first; before submitting, 
run all tests with `mvn -Prun-its verify` to check for regressions.
 + Submit a pull request to the repository in the Apache organization.
 
 If you plan to contribute on a regular basis, please consider filing a 
[contributor license agreement][cla].

Reply via email to