From af2ed13214dc92d979000f0d4912b57856156059 Mon Sep 17 00:00:00 2001 From: Jim Myhrberg Date: Fri, 29 Dec 2017 01:30:31 +0000 Subject: [PATCH] Update FAQ about descriptive names with ticket number recommendation --- common-flow.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/common-flow.md b/common-flow.md index 2d72fd8..762f7c0 100644 --- a/common-flow.md +++ b/common-flow.md @@ -299,8 +299,13 @@ is and what it does. Here's a few examples: Notice how none of these have any prefixes like "feature/" or "hotfix/", they're not needed when branch names are properly descriptive. However there's nothing -to say you can't use such prefixes if you want. That also means that you can add -ticket number prefixes if your team/org has that as part of it's process. +to say you can't use such prefixes if you want. + +You can also add ticket numbers to the branch name if your team/org has that as +part of it's process. But it is recommended that ticket numbers are added to the +end of the branch name. The ticket number is essentially metadata, so put it at +the end and out of the way of humans trying to read the descriptive name from +left to right. ### How do we release an emergency hotfix when the master branch is broken?