I have used a GitHub-PR header to refer to the GitHub pull request where
a patch originated in a couple of cases. This results in the commit
getting automatically linked back to the pull request on github.
Document this as a format that can be used to refer to pull requests.
Signed-off-by: Russell Bryant <russ...@ovn.org>
---
CONTRIBUTING.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1e1d573..c7ef13e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -216,6 +216,7 @@ Examples of common tags follow.
VMware-BZ: #1234567
ONF-JIRA: EXT-12345
+ GitHub-PR: #100
If a patch fixes or is otherwise related to a bug reported in
a private bug tracker, you may include some tracking ID for
@@ -223,6 +224,7 @@ Examples of common tags follow.
identifier to make the origin clear, e.g. "VMware-BZ" refers
to VMware's internal Bugzilla instance and "ONF-JIRA" refers
to the Open Networking Foundation's JIRA bug tracker.
+ “GitHub-PR” refers to a pull request for OVS on GitHub.
Bug #1234567.
Issue: 1234567
--
2.5.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
