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

garydgregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-parent.git


The following commit(s) were added to refs/heads/master by this push:
     new 24adcee  Clarify changelog placement and XML indentation guidelines
24adcee is described below

commit 24adcee3f10ff923a99e8e657c423cbff8a54f61
Author: Gary Gregory <[email protected]>
AuthorDate: Mon Oct 26 17:43:55 2026 -0400

    Clarify changelog placement and XML indentation guidelines
    
    Append new actions to the appropriate section of the unreleased release
    and preserve existing action order. Require spaces instead of tabs and
    2 spaces per XML nesting level.
---
 AGENTS.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index ca58514..a850d19 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -73,10 +73,17 @@ mvn -B -DskipTests -DskipITs -ntp
   Use commas, colons, parentheses, or a new sentence instead. This applies to
   HTML entities too (`&mdash;`).
 
+
 ### Commits
 
 - Use the `Assisted-By:` trailer (not `Co-Authored-By:`).
 
+## Non-Code & Metadata Files
+
+When editing `src/changes/changes.xml`, add new `action` elements to the 
current unreleased `release` element. Actions are grouped into sections 
introduced by comments such as `<!-- FIX -->`, `<!-- ADD -->`, and `<!-- UPDATE 
-->`. Append each new action to the appropriate section, immediately before the 
next section comment or the closing `</release>` tag. Preserve the order of 
existing actions.
+
+Use spaces for indentation, never tabs. Indent XML by 2 spaces per nesting 
level.
+
 ## Security
 
 Security model: [SECURITY.md](./SECURITY.md)

Reply via email to