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

[PATCH v5 2/2] repo: add new flag --keys to git-repo-info

From
Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date
Jan 23, 2026, 16:34 UTC
Message-ID
<20260123164900.35092-3-lucasseikioshiro@gmail.com>
In-Reply-To
<20260123164900.35092-1-lucasseikioshiro@gmail.com>

If the user wants to find what are the available keys, they need to either check the documentation or to ask for all the key-value pairs by using --all.

Add a new flag --keys for listing only the available keys without listing the values.

Signed-off-by: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
---
 Documentation/git-repo.adoc | 11 ++++++++++
 builtin/repo.c              | 32 +++++++++++++++++++++++++++++
 t/t1900-repo.sh             | 40 +++++++++++++++++++++++++++----------
 3 files changed, 72 insertions(+), 11 deletions(-)
diff --git a/Documentation/git-repo.adoc b/Documentation/git-repo.adoc
index 693e1bbced..f474274009 100644
--- a/Documentation/git-repo.adoc
+++ b/Documentation/git-repo.adoc
@@ -9,6 +9,7 @@ SYNOPSIS
 --------
 [synopsis]
 git repo info [--format=(lines|nul) | -z] [--all | <key>...]
+git repo info --keys [--format=(lines|nul) | -z]
 git repo structure [--format=(table|lines|nul) | -z]
 
 DESCRIPTION
@@ -45,6 +46,16 @@ supported:
 +
 `-z` is an alias for `--format=nul`.
 
+`info --keys [--format=(lines|nul) | -z]`::
+	List all the available keys, one per line. The output format can be chosen
+	through the flag `--format`. The following formats are supported:
++
+`lines`:::
+	output the keys one per line. This is the default.
+
+`nul`:::
+	similar to `lines`, but using a _NUL_ character after each value.
+
 `structure [--format=(table|lines|nul) | -z]`::
 	Retrieve statistics about the current repository structure. The
 	following kinds of information are reported:
diff --git a/builtin/repo.c b/builtin/repo.c
index 4031612bc8..a7d4855f06 100644
--- a/builtin/repo.c
+++ b/builtin/repo.c
@@ -18,6 +18,7 @@
 
 static const char *const repo_usage[] = {
 	"git repo info [--format=(lines|nul) | -z] [--all | <key>...]",
+	"git repo info --keys [--format=(lines|nul) | -z]",
 	"git repo structure [--format=(table|lines|nul) | -z]",
 	NULL
 };
@@ -148,6 +149,29 @@ static int print_all_fields(struct repository *repo,
 	return 0;
 }
 
+static int print_keys(enum output_format format)
+{
+	char sep;
+
+	switch (format) {
+	case FORMAT_LINES:
+		sep = '\n';
+		break;
+	case FORMAT_NUL_TERMINATED:
+		sep = '\0';
+		break;
+	default:
+		die(_("--keys can only be used with --format=lines or --format=nul"));
+	}
+
+	for (size_t i = 0; i < ARRAY_SIZE(repo_info_fields); i++) {
+		const struct field *field = &repo_info_fields[i];
+		printf("%s%c", field->key, sep);
+	}
+
+	return 0;
+}
+
 static int parse_format_cb(const struct option *opt,
 			   const char *arg, int unset UNUSED)
 {
@@ -172,6 +196,7 @@ static int cmd_repo_info(int argc, const char **argv, const char *prefix,
 {
 	enum output_format format = FORMAT_LINES;
 	int all_keys = 0;
+	int show_keys = 0;
 	struct option options[] = {
 		OPT_CALLBACK_F(0, "format", &format, N_("format"),
 			       N_("output format"),
@@ -181,11 +206,18 @@ static int cmd_repo_info(int argc, const char **argv, const char *prefix,
 			       PARSE_OPT_NONEG | PARSE_OPT_NOARG,
 			       parse_format_cb),
 		OPT_BOOL(0, "all", &all_keys, N_("print all keys/values")),
+		OPT_BOOL(0, "keys", &show_keys, N_("show keys")),
 		OPT_END()
 	};
 
 	argc = parse_options(argc, argv, prefix, options, repo_usage, 0);
 
+	if (show_keys && (all_keys || argc))
+		die(_("--keys cannot be used with a <key> or --all"));
+
+	if (show_keys)
+		return print_keys(format);
+
 	if (format != FORMAT_LINES && format != FORMAT_NUL_TERMINATED)
 		die(_("unsupported output format"));
 
diff --git a/t/t1900-repo.sh b/t/t1900-repo.sh
index 4155211e5d..a9eb07abe8 100755
--- a/t/t1900-repo.sh
+++ b/t/t1900-repo.sh
@@ -4,15 +4,6 @@ test_description='test git repo-info'
 
 . ./test-lib.sh
 
-# git-repo-info keys. It must contain the same keys listed in the const
-# repo_info_fields, in lexicographical order.
-REPO_INFO_KEYS='
-	layout.bare
-	layout.shallow
-	object.format
-	references.format
-'
-
 # Test whether a key-value pair is correctly returned
 #
 # Usage: test_repo_info <label> <init command> <repo_name> <key> <expected value>
@@ -119,8 +110,8 @@ test_expect_success 'git repo info uses the last requested format' '
 	test_cmp expected actual
 '
 
-test_expect_success 'git repo info --all returns all key-value pairs' '
-	git repo info $REPO_INFO_KEYS >expect &&
+test_expect_success 'git repo info --all and git repo info $(git repo info --keys) output the same data' '
+	git repo info $(git repo info --keys) >expect &&
 	git repo info --all >actual &&
 	test_cmp expect actual
 '
@@ -131,4 +122,31 @@ test_expect_success 'git repo info --all <key> aborts' '
 	test_cmp expect actual
 '
 
+test_expect_success 'git repo info --keys --format=nul uses nul-terminated output' '
+	git repo info --keys --format=lines >lines &&
+	lf_to_nul <lines >expect &&
+	git repo info --keys --format=nul >actual &&
+	test_cmp expect actual
+'
+
+test_expect_success 'git repo info --keys aborts when using --format other than lines or nul' '
+	echo "fatal: --keys can only be used with --format=lines or --format=nul" >expect &&
+	test_must_fail git repo info --keys --format=table 2>actual &&
+	test_cmp expect actual
+'
+
+test_expect_success 'git repo info --keys aborts when requesting keys' '
+	echo "fatal: --keys cannot be used with a <key> or --all" >expect &&
+	test_must_fail git repo info --keys --all 2>actual_all &&
+	test_must_fail git repo info --keys some.key 2>actual_key &&
+	test_cmp expect actual_all &&
+	test_cmp expect actual_key
+'
+
+test_expect_success 'git repo info --keys uses lines as its default output format' '
+	git repo info --keys --format=lines >expect &&
+	git repo info --keys >actual &&
+	test_cmp expect actual
+'
+
 test_done
-- 
2.50.1 (Apple Git-155)
Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 33 of 40 in “repo: add new flag --keys to git-repo-info”
  1. repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Dec 7, 2025
  2. Junio C HamanoDec 7, 2025
  3. Lucas Seiki OshiroDec 8, 2025
  4. Patrick SteinhardtDec 8, 2025
  5. 0/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Dec 9, 2025
  6. 1/2 repo: add a default output format to enum output_formatLucas Seiki Oshiro, Dec 9, 2025
  7. Patrick SteinhardtJan 5, 2026
  8. Lucas Seiki OshiroJan 7, 2026
  9. Patrick SteinhardtJan 8, 2026
  10. 2/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Dec 9, 2025
  11. Patrick SteinhardtJan 5, 2026
  12. Lucas Seiki OshiroJan 5, 2026
  13. Patrick SteinhardtJan 5, 2026
  14. 0/2 repo: add --format=default and --keysLucas Seiki Oshiro, Jan 9, 2026
  15. Junio C HamanoJan 10, 2026
  16. Junio C HamanoJan 10, 2026
  17. 1/2 repo: add a default output format to enum output_formatLucas Seiki Oshiro, Jan 9, 2026
  18. 2/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Jan 9, 2026
  19. Jean-Noël AVILAJan 10, 2026
  20. Lucas Seiki OshiroJan 10, 2026
  21. Patrick SteinhardtJan 12, 2026
  22. 0/2 repo: add --format=default and --keysLucas Seiki Oshiro, Jan 19, 2026
  23. 1/2 repo: add a default output format to enum output_formatLucas Seiki Oshiro, Jan 19, 2026
  24. 2/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Jan 19, 2026
  25. Patrick SteinhardtJan 20, 2026
  26. Lucas Seiki OshiroJan 20, 2026
  27. Patrick SteinhardtJan 21, 2026
  28. Lucas Seiki OshiroJan 21, 2026
  29. Junio C HamanoJan 20, 2026
  30. 0/2 repo: add --keys and rename "keyvalue" to "lines"Lucas Seiki Oshiro, Jan 23, 2026
  31. 1/2 repo: rename "keyvalue" to "lines"Lucas Seiki Oshiro, Jan 23, 2026
  32. Patrick SteinhardtJan 27, 2026
  33. 2/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Jan 23, 2026
  34. Patrick SteinhardtJan 27, 2026
  35. Lucas Seiki OshiroJan 27, 2026
  36. 0/2 repo: add --keys and rename "keyvalue" to "lines"Lucas Seiki Oshiro, Feb 14, 2026
  37. 1/2 repo: rename the output format "keyvalue" to "lines"Lucas Seiki Oshiro, Feb 14, 2026
  38. 2/2 repo: add new flag --keys to git-repo-infoLucas Seiki Oshiro, Feb 14, 2026
  39. Junio C HamanoFeb 14, 2026
  40. Patrick SteinhardtFeb 16, 2026

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.