From 5dbf8ec801a9da8e6d45dfc46a70568c99a73d95 Mon Sep 17 00:00:00 2001
From: Alexis DRAI <alexis.drai@etu.uca.fr>
Date: Sat, 21 Jan 2023 10:36:24 +0100
Subject: [PATCH] Revert prev commit

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b11983f..a4204bb 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@ git reset --hard origin/master
 
 Give your new branch a name referring to an issue (or maybe a group of similar issues)
 ```
-git checkout -b branch-name-that-describes-the-new-feature
+git checkout -b new-feature
 ```
 
 Regularly, you might want to get all the new code from your master (yeah, we forgot to rename it "main", sorry) branch, to work with an up-to-date codebase: