From d613ba0593e318a6af0f27c68e0b847740485158 Mon Sep 17 00:00:00 2001 From: Matt Lewandowsky Date: Fri, 5 Apr 2013 04:57:09 -0700 Subject: [PATCH] Provide guidance for cross-repo issue referencing --- docs/en/misc/contributing/code.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/en/misc/contributing/code.md b/docs/en/misc/contributing/code.md index 6576a17e2..339cc6519 100644 --- a/docs/en/misc/contributing/code.md +++ b/docs/en/misc/contributing/code.md @@ -228,6 +228,10 @@ One thing you do not want to do is to issue a git commit with the -a option. Thi $ git commit -a +Sometimes, you might correct an issue which was reported in a different repo. In these cases, don't simply refer to the issue number as GitHub will infer that as correcting an issue in the current repo. In these cases, use the full GitHub path to reference the issue. + + $ git commit -m 'Issue silverstripe/silverstripe-cms#100: Some kind of descriptive message' + ## What is git rebase? Using `git rebase` helps create clean commit trees and makes keeping your code up-to-date with the current state of the upstream master easy. Here's how it works.