You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by gg...@apache.org on 2022/09/01 11:52:21 UTC
[commons-configuration] branch master updated: Refer to master branch only and drop reference to trunk branch name
This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-configuration.git
The following commit(s) were added to refs/heads/master by this push:
new 6bbb45f7 Refer to master branch only and drop reference to trunk branch name
6bbb45f7 is described below
commit 6bbb45f756bfbb2215d535a6766858e097d4a081
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Thu Sep 1 07:52:02 2022 -0400
Refer to master branch only and drop reference to trunk branch name
---
CONTRIBUTING.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b6f59137..465e00cb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -61,7 +61,7 @@ Making Changes
--------------
+ Create a _topic branch_ for your isolated work.
- * Usually you should base your branch on the `master` or `trunk` branch.
+ * Usually you should base your branch on the `master` branch.
* A good topic branch name can be the JIRA bug id plus a keyword, e.g. `CONFIGURATION-123-InputStream`.
* If you have submitted multiple JIRA issues, try to maintain separate branches and pull requests.
+ Make commits of logical units.