You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@solr.apache.org by ep...@apache.org on 2021/04/15 18:54:13 UTC
[solr] branch main updated: document handling central versus
private branches (#79)
This is an automated email from the ASF dual-hosted git repository.
epugh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/main by this push:
new b574364 document handling central versus private branches (#79)
b574364 is described below
commit b5743645dbe62a2ea4e31645b97a03d95c7377e7
Author: Eric Pugh <ep...@opensourceconnections.com>
AuthorDate: Thu Apr 15 14:54:04 2021 -0400
document handling central versus private branches (#79)
Co-authored-by: epugh@opensourceconnections.com <>
---
dev-docs/FAQ.adoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/dev-docs/FAQ.adoc b/dev-docs/FAQ.adoc
index 1ea1aa1..5d6b004 100644
--- a/dev-docs/FAQ.adoc
+++ b/dev-docs/FAQ.adoc
@@ -9,3 +9,12 @@ This document provides a quick reference for frequently questioned concepts and
=== What do I do with NOTICE.txt if I don't have one to satisfy Gradle?
You create an empty file, similar to the `/solr/licenses/antlr4-runtime-NOTICE.txt`
+
+=== What are best practices for branches in Git?
+
+Most committers already use a private fork branch for PRs. Use of central branches
+is ok for very collaborative work, but 95% of the time it is better to use a private
+branch to avoid extra mailing list traffic etc.
+
+Periodically review https://github.com/apache/solr/branches/all to see if you have
+created a branch that can be deleted.