From: "Husain Sitamuwala via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Husain Sitamuwala <husainsitamuwala21@gmail.com>,
Hussain Sitamouwala <husainsitamuwala21@gmail.com>
Subject: [PATCH] check-ref-format: use parse-options API
Date: Thu, 29 Oct 2026 18:33:27 +0000 [thread overview]
Message-ID: <pull.2470.git.git.1793298807397.gitgitgadget@gmail.com> (raw)
From: Hussain Sitamouwala <husainsitamuwala21@gmail.com>
Use the parse-options API to handle command-line options
consistently with other Git builtins.
The command currently parses options manually, duplicating
argument-handling logic. Using parse-options makes option
handling consistent with the rest of Git.
Replace manual option parsing while preserving support for
normalization, branch names, and refname validation.
Signed-off-by: Hussain Sitamouwala <husainsitamuwala21@gmail.com>
---
check-ref-format: use parse-options API
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2470%2FCodeWithHusain%2Foutreachy-microproject-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2470/CodeWithHusain/outreachy-microproject-v1
Pull-Request: https://github.com/git/git/pull/2470
builtin/check-ref-format.c | 45 ++++++++++++++++++++++++--------------
1 file changed, 28 insertions(+), 17 deletions(-)
diff --git a/builtin/check-ref-format.c b/builtin/check-ref-format.c
index fd1c9c0e0c..58e60eecd2 100644
--- a/builtin/check-ref-format.c
+++ b/builtin/check-ref-format.c
@@ -5,13 +5,20 @@
#define USE_THE_REPOSITORY_VARIABLE
#include "builtin.h"
+#include "parse-options.h"
#include "refs.h"
#include "setup.h"
#include "strbuf.h"
static const char builtin_check_ref_format_usage[] =
-"git check-ref-format [--normalize] [<options>] <refname>\n"
-" or: git check-ref-format --branch <branchname-shorthand>";
+ "git check-ref-format [--normalize] [<options>] <refname>\n"
+ " or: git check-ref-format --branch <branchname-shorthand>";
+
+static const char * const builtin_check_ref_format_usages[] = {
+ "git check-ref-format [--normalize] [<options>] <refname>",
+ " or: git check-ref-format --branch <branchname-shorthand>",
+ NULL
+};
/*
* Return a copy of refname but with leading slashes removed and runs
@@ -58,13 +65,26 @@ int cmd_check_ref_format(int argc,
const char *prefix,
struct repository *repo UNUSED)
{
- int i;
int normalize = 0;
int flags = 0;
const char *refname;
char *to_free = NULL;
int ret = 1;
+ struct option options[] = {
+ OPT_BOOL(0, "normalize", &normalize,
+ N_("normalize refname")),
+ OPT_BOOL(0, "print", &normalize,
+ N_("print normalized refname")),
+ OPT_BIT(0, "allow-onelevel", &flags,
+ N_("allow one-level refnames"),
+ REFNAME_ALLOW_ONELEVEL),
+ OPT_BIT(0, "refspec-pattern", &flags,
+ N_("allow refspec patterns"),
+ REFNAME_REFSPEC_PATTERN),
+ OPT_END()
+ };
+
BUG_ON_NON_EMPTY_PREFIX(prefix);
show_usage_if_asked(argc, argv,
@@ -73,22 +93,13 @@ int cmd_check_ref_format(int argc,
if (argc == 3 && !strcmp(argv[1], "--branch"))
return check_ref_format_branch(argv[2]);
- for (i = 1; i < argc && argv[i][0] == '-'; i++) {
- if (!strcmp(argv[i], "--normalize") || !strcmp(argv[i], "--print"))
- normalize = 1;
- else if (!strcmp(argv[i], "--allow-onelevel"))
- flags |= REFNAME_ALLOW_ONELEVEL;
- else if (!strcmp(argv[i], "--no-allow-onelevel"))
- flags &= ~REFNAME_ALLOW_ONELEVEL;
- else if (!strcmp(argv[i], "--refspec-pattern"))
- flags |= REFNAME_REFSPEC_PATTERN;
- else
- usage(builtin_check_ref_format_usage);
- }
- if (! (i == argc - 1))
+ argc = parse_options(argc, argv, prefix, options,
+ builtin_check_ref_format_usages, 0);
+
+ if (argc != 1)
usage(builtin_check_ref_format_usage);
- refname = argv[i];
+ refname = argv[0];
if (normalize)
refname = to_free = collapse_slashes(refname);
if (check_refname_format(refname, flags))
base-commit: 37b3475fb530c14109211faca33716a173db61ed
--
gitgitgadget
next reply other threads:[~2026-10-29 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 18:33 Husain Sitamuwala via GitGitGadget [this message]
2026-10-29 20:09 ` [PATCH] check-ref-format: use parse-options API Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.2470.git.git.1793298807397.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=husainsitamuwala21@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox