[xen master] docs/process: branching-checklist: Clarify steps to add the branch in osstest

[patchbot@xxxxxxx]

commit 4e0e7a29d2fe318e4e60e77a56773b4d020ebc6a
Author:     Julien Grall <jgrall@xxxxxxxxxx>
AuthorDate: Thu Feb 9 17:07:28 2023 +0000
Commit:     Julien Grall <jgrall@xxxxxxxxxx>
CommitDate: Thu Feb 9 17:07:28 2023 +0000

    docs/process: branching-checklist: Clarify steps to add the branch in 
osstest
    
    The steps to add the new branch in osstest doesn't mention the change
    should be committed.
    
    Update the steps to clarify that. Take the opportunity to switch to
    use $v instead hardcoded version.
    
    Signed-off-by: Julien Grall <jgrall@xxxxxxxxxx>
    Reviewed-by: Henry Wang <Henry.Wang@xxxxxxx>
---
 docs/process/branching-checklist.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/process/branching-checklist.txt 
b/docs/process/branching-checklist.txt
index a98f6559ab..d1550385c9 100644
--- a/docs/process/branching-checklist.txt
+++ b/docs/process/branching-checklist.txt
@@ -49,7 +49,9 @@ ov=4.0
     OSSTEST_CONFIG=production-config-cambridge ./mg-branch-setup 
qemu-upstream-$v-testing bisect
 
 * add branch to osstest
-    ie add both eg qemu-upstream-4.2-testing and xen-4.2-testing to BRANCHES 
in cr-for-branches
+    Add both qemu-upstream-$v-testing and xen-$v-testing to BRANCHES in 
cr-for-branches
+    git add -p
+    git commit -m "cr-for-branches: Add Xen and QEMU $v branch"
 
 * add to patchbot
     on xenbits
--
generated by git-patchbot for /home/xen/git/xen.git#master