From 1f98bf46a594fcdec6e80a6b1ff755c36a88b20e Mon Sep 17 00:00:00 2001 From: Neil Lathwood Date: Tue, 15 Aug 2017 15:59:58 +0100 Subject: [PATCH] Update Using-Git.md (#7159) --- doc/Developing/Using-Git.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/Developing/Using-Git.md b/doc/Developing/Using-Git.md index a0d21433a8..4a410dadde 100644 --- a/doc/Developing/Using-Git.md +++ b/doc/Developing/Using-Git.md @@ -70,9 +70,7 @@ Now, create a new branch to do you work on. It's important that you do this as y one feature at a time and submit them as pull requests individually. If you did all your work in the master branch then it gets a bit messy! -Ideally you want to create your new branch name based of the issue number. So firstly create an issue on -[GitHub](https://github.com/librenms/librenms/issues) so that others are aware of the work going on. If the issue number -you created is 123 then use issue-123 as the branch name. +You need to give you branch a name. If an issue is open (or closed on GitHub) then you can use that, in this example if the issue number is 123 then we will use issue-123. If a post exists on the community forum then you can use the post id like community-123. You're also welcome to use any arbitrary name for your branch but try and make it relevant to what the branch is. ```bash git checkout -b issue-123