The test-config helper can return at least three different exit codes to
reflect the status of the requested operation. And these codes are
checked in some of the tests. But there is an inconsistent place in the
helper where an usage error returns the same code as a "value not found"
error. Let's fix that and, while we are here, document the meaning of
each exit code in the file's header.
Signed-off-by: Matheus Tavares <matheus.bernardino@xxxxxx>
---
t/helper/test-config.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/t/helper/test-config.c b/t/helper/test-config.c
index a6e936721f..9e9d50099a 100644
--- a/t/helper/test-config.c
+++ b/t/helper/test-config.c
@@ -30,6 +30,11 @@
* iterate -> iterate over all values using git_config(), and print some
* data for each
*
+ * Exit codes:
+ * 0: success
+ * 1: value not found for the given config key
+ * 2: config file path given as argument is inaccessible or doesn't exist
+ *
* Examples:
*
* To print the value with highest priority for key "foo.bAr Baz.rock":
@@ -80,10 +85,10 @@ int cmd__config(int argc, const char **argv)
git_configset_init(&cs);
- if (argc < 2) {
- fprintf(stderr, "Please, provide a command name on the command-line\n");
- goto exit1;
- } else if (argc == 3 && !strcmp(argv[1], "get_value")) {
+ if (argc < 2)
+ die("Please, provide a command name on the command-line");
+
+ if (argc == 3 && !strcmp(argv[1], "get_value")) {
if (!git_config_get_value(argv[2], &v)) {
if (!v)
printf("(NULL)\n");
--
2.28.0
