This is an automated email from the ASF dual-hosted git repository.
mridulpathak pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ofbiz-plugins.git
The following commit(s) were added to refs/heads/trunk by this push:
new be306669e Document the commit message format in the contribution
workflow skill
be306669e is described below
commit be306669efdea3d0d02a33271d5a4895fd2466fc
Author: Mridul Pathak <[email protected]>
AuthorDate: Sat Oct 24 14:42:24 2026 +0530
Document the commit message format in the contribution workflow skill
Commit messages now follow section 5 of CONTRIBUTING.md (a short imperative
title, without the pull request prefix and the JIRA ticket), while pull request
titles and descriptions keep the pull request template. The skill described a
single format for both.
---
.../manage-contribution-workflow/SKILL.md | 22 ++++++++++++++++++++--
1 file changed, 20 insertions(+), 2 deletions(-)
diff --git a/ai-agent-skills/manage-contribution-workflow/SKILL.md
b/ai-agent-skills/manage-contribution-workflow/SKILL.md
index 5562d2969..0992d572d 100644
--- a/ai-agent-skills/manage-contribution-workflow/SKILL.md
+++ b/ai-agent-skills/manage-contribution-workflow/SKILL.md
@@ -246,8 +246,26 @@ In the backport PR description, say "Backported from trunk
(#<PR-number>)"
either way, and note if it required manual adaptation rather than a clean
cherry-pick.
+## Commit Message Conventions
+
+Follow section 5 of `CONTRIBUTING.md`, which no longer uses the pull request
+title format for commits:
+
+- Title: a short line in the imperative mood that says what the commit does
+ (for example "Fix rounding issue in order calculation"), without a trailing
+ period. No `Fixed:`/`Improved:` prefix and no JIRA ticket: those belong to
+ the pull request title.
+- Body, only when context is needed: a blank line, then a short paragraph on
+ why the change was made, important implementation details or side effects.
+ When one commit groups several distinct fixes, list them as bullets.
+- A `Thanks:` line may end the body, under the same conditions as in the pull
+ request description.
+- Keep commits focused and avoid mixing unrelated changes.
+
## Pull Request Conventions
+Follow `.github/pull_request_template.md`.
+
Title: one of `Improved:` / `Implemented:` / `Documented:` / `Completed:` /
`Reverted:` / `Fixed:`, followed by a short description, ending with
`(OFBIZ-XXXXX)` when an issue exists.
@@ -271,8 +289,8 @@ changed.
- Don't hand-reapply a diff for a backport when cherry-pick is available.
- Don't block a change on filing a JIRA issue when the contributor (e.g. a
committer) doesn't need one — but do suggest filing one for anything
- non-trivial, since it's what ties the PR title, commit history, and
- release notes together.
+ non-trivial, since it's what ties the PR title and the release notes
+ together.
## See Also
- `coding-standards` — OFBiz style and idiom rules to follow while writing the
change.
