git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 2/2] branch: Mark and colorize a branch differently if it is checked out in a linked worktree

From
nbelakovski@gmail.com <nbelakovski@gmail.com>
Date
Nov 11, 2018, 23:58 UTC
Message-ID
<20181111235831.44824-3-nbelakovski@gmail.com>
In-Reply-To
<20181111235831.44824-1-nbelakovski@gmail.com>
From: Nickolai Belakovski <nbelakovski@gmail.com>

In order to more clearly display which branches are active, the output of git branch is modified to mark branches checkout out in a linked worktree with a "+" and color them in a faint light green (in contrast to the current branch, which will still be denoted with a "*" and colored in green)

This is meant to simplify workflows related to worktree, particularly due to the limitations of not being able to check out the same branch in two worktrees and the inability to delete a branch checked out in a worktree. When performing branch operations like checkout and delete, it would be useful to know more readily if the branches in which the user is interested are already checked out in a worktree.

The git worktree list command contains the relevant information, however this is a much less frquently used command than git branch.

Signed-off-by: Nickolai Belakovski <nbelakovski@gmail.com>
---
 builtin/branch.c         | 22 +++++++++++++---------
 color.h                  | 18 ++++++++++++++++++
 t/t3200-branch.sh        |  8 ++++----
 t/t3203-branch-output.sh | 21 +++++++++++++++++++++
 t/test-lib-functions.sh  |  6 ++++++
 5 files changed, 62 insertions(+), 13 deletions(-)
diff --git a/builtin/branch.c b/builtin/branch.c
index 0c55f7f065..34f44c82d7 100644
--- a/builtin/branch.c
+++ b/builtin/branch.c
@@ -42,11 +42,12 @@ static struct object_id head_oid;
 static int branch_use_color = -1;
 static char branch_colors[][COLOR_MAXLEN] = {
 	GIT_COLOR_RESET,
-	GIT_COLOR_NORMAL,       /* PLAIN */
-	GIT_COLOR_RED,          /* REMOTE */
-	GIT_COLOR_NORMAL,       /* LOCAL */
-	GIT_COLOR_GREEN,        /* CURRENT */
-	GIT_COLOR_BLUE,         /* UPSTREAM */
+	GIT_COLOR_NORMAL,             /* PLAIN */
+	GIT_COLOR_RED,                /* REMOTE */
+	GIT_COLOR_NORMAL,             /* LOCAL */
+	GIT_COLOR_GREEN,              /* CURRENT */
+	GIT_COLOR_BLUE,               /* UPSTREAM */
+	GIT_COLOR_FAINT_LIGHT_GREEN,  /* WORKTREE */
 };
 enum color_branch {
 	BRANCH_COLOR_RESET = 0,
@@ -54,7 +55,8 @@ enum color_branch {
 	BRANCH_COLOR_REMOTE = 2,
 	BRANCH_COLOR_LOCAL = 3,
 	BRANCH_COLOR_CURRENT = 4,
-	BRANCH_COLOR_UPSTREAM = 5
+	BRANCH_COLOR_UPSTREAM = 5,
+	BRANCH_COLOR_WORKTREE = 6
 };
 
 static const char *color_branch_slots[] = {
@@ -64,6 +66,7 @@ static const char *color_branch_slots[] = {
 	[BRANCH_COLOR_LOCAL]	= "local",
 	[BRANCH_COLOR_CURRENT]	= "current",
 	[BRANCH_COLOR_UPSTREAM] = "upstream",
+	[BRANCH_COLOR_WORKTREE] = "worktree",
 };
 
 static struct string_list output = STRING_LIST_INIT_DUP;
@@ -342,9 +345,10 @@ static char *build_format(struct ref_filter *filter, int maxwidth, const char *r
 	struct strbuf local = STRBUF_INIT;
 	struct strbuf remote = STRBUF_INIT;
 
-	strbuf_addf(&local, "%%(if)%%(HEAD)%%(then)* %s%%(else)  %s%%(end)",
-		    branch_get_color(BRANCH_COLOR_CURRENT),
-		    branch_get_color(BRANCH_COLOR_LOCAL));
+	strbuf_addf(&local, "%%(if)%%(HEAD)%%(then)* %s%%(else)%%(if)%%(worktree)%%(then)+ %s%%(else)  %s%%(end)%%(end)",
+			branch_get_color(BRANCH_COLOR_CURRENT),
+			branch_get_color(BRANCH_COLOR_WORKTREE),
+			branch_get_color(BRANCH_COLOR_LOCAL));
 	strbuf_addf(&remote, "  %s",
 		    branch_get_color(BRANCH_COLOR_REMOTE));
 
diff --git a/color.h b/color.h
index 98894d6a17..857653df73 100644
--- a/color.h
+++ b/color.h
@@ -42,6 +42,24 @@ struct strbuf;
 #define GIT_COLOR_FAINT_BLUE	"\033[2;34m"
 #define GIT_COLOR_FAINT_MAGENTA	"\033[2;35m"
 #define GIT_COLOR_FAINT_CYAN	"\033[2;36m"
+#define GIT_COLOR_LIGHT_RED	"\033[91m"
+#define GIT_COLOR_LIGHT_GREEN	"\033[92m"
+#define GIT_COLOR_LIGHT_YELLOW	"\033[93m"
+#define GIT_COLOR_LIGHT_BLUE	"\033[94m"
+#define GIT_COLOR_LIGHT_MAGENTA	"\033[95m"
+#define GIT_COLOR_LIGHT_CYAN	"\033[96m"
+#define GIT_COLOR_BOLD_LIGHT_RED	"\033[1;91m"
+#define GIT_COLOR_BOLD_LIGHT_GREEN	"\033[1;92m"
+#define GIT_COLOR_BOLD_LIGHT_YELLOW	"\033[1;93m"
+#define GIT_COLOR_BOLD_LIGHT_BLUE	"\033[1;94m"
+#define GIT_COLOR_BOLD_LIGHT_MAGENTA	"\033[1;95m"
+#define GIT_COLOR_BOLD_LIGHT_CYAN	"\033[1;96m"
+#define GIT_COLOR_FAINT_LIGHT_RED	"\033[2;91m"
+#define GIT_COLOR_FAINT_LIGHT_GREEN	"\033[2;92m"
+#define GIT_COLOR_FAINT_LIGHT_YELLOW	"\033[2;93m"
+#define GIT_COLOR_FAINT_LIGHT_BLUE	"\033[2;94m"
+#define GIT_COLOR_FAINT_LIGHT_MAGENTA	"\033[2;95m"
+#define GIT_COLOR_FAINT_LIGHT_CYAN	"\033[2;96m"
 #define GIT_COLOR_BG_RED	"\033[41m"
 #define GIT_COLOR_BG_GREEN	"\033[42m"
 #define GIT_COLOR_BG_YELLOW	"\033[43m"
diff --git a/t/t3200-branch.sh b/t/t3200-branch.sh
index 478b82cf9b..e404f6e23c 100755
--- a/t/t3200-branch.sh
+++ b/t/t3200-branch.sh
@@ -292,7 +292,7 @@ test_expect_success 'git branch --list -v with --abbrev' '
 test_expect_success 'git branch --column' '
 	COLUMNS=81 git branch --column=column >actual &&
 	cat >expected <<\EOF &&
-  a/b/c     bam       foo       l       * master    n         o/p       r
+  a/b/c   + bam       foo       l       * master    n         o/p       r
   abc       bar       j/k       m/m       master2   o/o       q
 EOF
 	test_cmp expected actual
@@ -307,7 +307,7 @@ test_expect_success 'git branch --column with an extremely long branch name' '
 	cat >expected <<EOF &&
   a/b/c
   abc
-  bam
++ bam
   bar
   foo
   j/k
@@ -332,7 +332,7 @@ test_expect_success 'git branch with column.*' '
 	git config --unset column.branch &&
 	git config --unset column.ui &&
 	cat >expected <<\EOF &&
-  a/b/c   bam   foo   l   * master    n     o/p   r
+  a/b/c + bam   foo   l   * master    n     o/p   r
   abc     bar   j/k   m/m   master2   o/o   q
 EOF
 	test_cmp expected actual
@@ -349,7 +349,7 @@ test_expect_success 'git branch -v with column.ui ignored' '
 	cat >expected <<\EOF &&
   a/b/c
   abc
-  bam
++ bam
   bar
   foo
   j/k
diff --git a/t/t3203-branch-output.sh b/t/t3203-branch-output.sh
index ee6787614c..06771fac64 100755
--- a/t/t3203-branch-output.sh
+++ b/t/t3203-branch-output.sh
@@ -240,6 +240,27 @@ test_expect_success 'git branch --format option' '
 	test_i18ncmp expect actual
 '
 
+test_expect_success '"add" a worktree' '
+	mkdir worktree_dir &&
+	git worktree add -b master_worktree worktree_dir master
+'
+
+cat >expect <<'EOF'
+* <GREEN>(HEAD detached from fromtag)<RESET>
+  ambiguous<RESET>
+  branch-one<RESET>
+  branch-two<RESET>
+  master<RESET>
++ <FAINT;LGREEN>master_worktree<RESET>
+  ref-to-branch<RESET> -> branch-one
+  ref-to-remote<RESET> -> origin/branch-one
+EOF
+test_expect_success TTY 'worktree colors correct' '
+	test_terminal git branch >actual.raw &&
+	test_decode_color <actual.raw >actual &&
+	test_cmp expect actual
+'
+
 test_expect_success "set up color tests" '
 	echo "<RED>master<RESET>" >expect.color &&
 	echo "master" >expect.bare &&
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index 78d8c3783b..2831a42a88 100644
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -61,6 +61,12 @@ test_decode_color () {
 			if (n == 45) return "BMAGENTA";
 			if (n == 46) return "BCYAN";
 			if (n == 47) return "BWHITE";
+			if (n == 91) return "LRED";
+			if (n == 92) return "LGREEN";
+			if (n == 93) return "LYELLOW";
+			if (n == 94) return "LBLUE";
+			if (n == 95) return "LMAGENTA";
+			if (n == 96) return "LCYAN";
 		}
 		{
 			while (match($0, /\033\[[0-9;]*m/) != 0) {
-- 
2.14.2
Previous: Jeff KingNext: Junio C Hamano
Message 27 of 125 in “branch: colorize branches checked out in a linked working tree the same way as the current branch is colorized”
  1. branch: colorize branches checked out in a linked working tree the same way as the current branch is colorizedNickolai Belakovski, Sep 27, 2018
  2. Ævar Arnfjörð BjarmasonSep 27, 2018
  3. Nickolai BelakovskiSep 27, 2018
  4. Duy NguyenSep 27, 2018
  5. Jeff KingSep 27, 2018
  6. Nickolai BelakovskiSep 27, 2018
  7. Jeff KingSep 27, 2018
  8. Rafael AscensãoSep 27, 2018
  9. Jeff KingSep 27, 2018
  10. Jeff KingSep 27, 2018
  11. Junio C HamanoSep 27, 2018
  12. Jeff KingSep 28, 2018
  13. Junio C HamanoSep 28, 2018
  14. Rafael AscensãoSep 27, 2018
  15. Jeff KingSep 28, 2018
  16. Ævar Arnfjörð BjarmasonSep 27, 2018
  17. Nickolai BelakovskiSep 27, 2018
  18. Rafael AscensãoSep 27, 2018
  19. 0/2 refactoring branch colorization to ref-filternbelakovski@gmail.com, Nov 11, 2018
  20. 1/2 ref-filter: add worktree atomnbelakovski@gmail.com, Nov 11, 2018
  21. Junio C HamanoNov 12, 2018
  22. Jeff KingNov 12, 2018
  23. Junio C HamanoNov 13, 2018
  24. Nickolai BelakovskiNov 21, 2018
  25. Jeff KingNov 21, 2018
  26. Jeff KingNov 12, 2018
  27. 2/2 branch: Mark and colorize a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Nov 11, 2018
  28. Junio C HamanoNov 12, 2018
  29. Jeff KingNov 12, 2018
  30. Rafael AscensãoNov 12, 2018
  31. Junio C HamanoNov 13, 2018
  32. Jeff KingNov 13, 2018
  33. Nickolai BelakovskiNov 21, 2018
  34. 0/3 nbelakovski@gmail.com, Dec 16, 2018
  35. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Dec 16, 2018
  36. Jeff KingDec 18, 2018
  37. Nickolai BelakovskiDec 20, 2018
  38. Jeff KingDec 20, 2018
  39. 0/3 nbelakovski@gmail.com, Dec 24, 2018
  40. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Dec 24, 2018
  41. Jeff KingJan 3, 2019
  42. Eric SunshineJan 3, 2019
  43. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Dec 24, 2018
  44. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Dec 24, 2018
  45. Jeff KingJan 3, 2019
  46. Jeff KingJan 3, 2019
  47. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Dec 16, 2018
  48. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Dec 16, 2018
  49. Jeff KingDec 18, 2018
  50. 0/3 nbelakovski@gmail.com, Jan 6, 2019
  51. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Jan 6, 2019
  52. Junio C HamanoJan 7, 2019
  53. Nickolai BelakovskiJan 18, 2019
  54. Nickolai BelakovskiJan 18, 2019
  55. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Jan 6, 2019
  56. Junio C HamanoJan 7, 2019
  57. Philip OakleyJan 10, 2019
  58. Nickolai BelakovskiJan 13, 2019
  59. Junio C HamanoJan 14, 2019
  60. Nickolai BelakovskiJan 18, 2019
  61. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Jan 6, 2019
  62. Junio C HamanoJan 7, 2019
  63. 0/3 nbelakovski@gmail.com, Jan 22, 2019
  64. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Jan 22, 2019
  65. Junio C HamanoJan 23, 2019
  66. Nickolai BelakovskiJan 23, 2019
  67. Junio C HamanoJan 24, 2019
  68. Jeff KingJan 24, 2019
  69. Junio C HamanoJan 24, 2019
  70. Jeff KingJan 24, 2019
  71. Junio C HamanoJan 24, 2019
  72. Jeff KingJan 24, 2019
  73. Nickolai BelakovskiJan 31, 2019
  74. Jeff KingJan 31, 2019
  75. Junio C HamanoJan 31, 2019
  76. Jeff KingJan 31, 2019
  77. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Jan 22, 2019
  78. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Jan 22, 2019
  79. 0/3 nbelakovski@gmail.com, Feb 1, 2019
  80. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Feb 1, 2019
  81. Eric SunshineFeb 1, 2019
  82. Nickolai BelakovskiFeb 1, 2019
  83. Junio C HamanoFeb 4, 2019
  84. Nickolai BelakovskiFeb 18, 2019
  85. Junio C HamanoFeb 1, 2019
  86. 2/3 branch: Mark and color a branch differently if it is checked out in a linked worktreenbelakovski@gmail.com, Feb 1, 2019
  87. Junio C HamanoFeb 1, 2019
  88. Nickolai BelakovskiFeb 1, 2019
  89. Junio C HamanoFeb 4, 2019
  90. 3/3 branch: Add an extra verbose output displaying worktree path for refs checked out in a linked worktreenbelakovski@gmail.com, Feb 1, 2019
  91. Eric SunshineFeb 1, 2019
  92. Nickolai BelakovskiFeb 1, 2019
  93. Junio C HamanoFeb 1, 2019
  94. Nickolai BelakovskiFeb 1, 2019
  95. [RFC] Sample of test for git branch -vvnbelakovski@gmail.com, Feb 2, 2019
  96. Junio C HamanoFeb 1, 2019
  97. Nickolai BelakovskiFeb 1, 2019
  98. 0/3 nbelakovski@gmail.com, Feb 19, 2019
  99. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Feb 19, 2019
  100. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Feb 19, 2019
  101. Jeff KingFeb 21, 2019
  102. Nickolai BelakovskiMar 14, 2019
  103. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Feb 19, 2019
  104. Jeff KingFeb 21, 2019
  105. Nickolai BelakovskiMar 14, 2019
  106. Junio C HamanoMar 18, 2019
  107. Jeff KingFeb 21, 2019
  108. Nickolai BelakovskiMar 14, 2019
  109. 0/3 nbelakovski@gmail.com, Mar 16, 2019
  110. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Mar 16, 2019
  111. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Mar 16, 2019
  112. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Mar 16, 2019
  113. SZEDER GáborMar 18, 2019
  114. Junio C HamanoMar 18, 2019
  115. 0/3 nbelakovski@gmail.com, Apr 29, 2019
  116. 1/3 ref-filter: add worktreepath atomnbelakovski@gmail.com, Apr 29, 2019
  117. 2/3 branch: update output to include worktree infonbelakovski@gmail.com, Apr 29, 2019
  118. 3/3 branch: add worktree info on verbose outputnbelakovski@gmail.com, Apr 29, 2019
  119. SZEDER GáborApr 29, 2019
  120. Nickolai BelakovskiApr 29, 2019
  121. Johannes SchindelinApr 29, 2019
  122. Nickolai BelakovskiApr 29, 2019
  123. Ævar Arnfjörð BjarmasonSep 27, 2018
  124. Johannes SchindelinOct 2, 2018
  125. Johannes SchindelinApr 30, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.