From: Fien Dora <fiendora5@gmail.com>
To: git@vger.kernel.org
Cc: christian.couder@gmail.com, siddharthasthana31@gmail.com,
phillip.wood123@gmail.com
Subject: [Outreachy PATCH] t1402: test --no-allow-onelevel option precedence
Date: Mon, 26 Oct 2026 14:25:25 +0100 [thread overview]
Message-ID: <20261026132525.45414-1-fiendora5@gmail.com> (raw)
Git allows later command-line options to override earlier ones.
Added tests to verify that --no-allow-onelevel overrides
--allow-onelevel and vice versa.
This ensures that the expected behavior is preserved if the
argument-parsing code changes in the future.
Signed-off-by: Fien Dora <fiendora5@gmail.com>
---
t/t1402-check-ref-format.sh | 2 ++
1 file changed, 2 insertions(+)
diff --git a/t/t1402-check-ref-format.sh b/t/t1402-check-ref-format.sh
index 9dd64662b2..6036df0210 100755
--- a/t/t1402-check-ref-format.sh
+++ b/t/t1402-check-ref-format.sh
@@ -74,6 +74,8 @@ invalid_ref 'heads/foo*/bar*' --refspec-pattern
ref='foo'
invalid_ref "$ref"
valid_ref "$ref" --allow-onelevel
+invalid_ref "$ref" '--allow-onelevel --no-allow-onelevel'
+valid_ref "$ref" '--no-allow-onelevel --allow-onelevel'
invalid_ref "$ref" --refspec-pattern
valid_ref "$ref" '--refspec-pattern --allow-onelevel'
invalid_ref "$ref" --normalize
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-10-26 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:25 Fien Dora [this message]
2026-10-26 21:06 ` [Outreachy PATCH] t1402: test --no-allow-onelevel option precedence Junio C Hamano
2026-10-27 11:56 ` Fien Dora
2026-10-27 16:29 ` Junio C Hamano
2026-10-28 19:49 ` Fien Dora
2026-10-28 20:00 ` Fien Dora
2026-10-27 14:54 ` [Outreachy PATCH v2] " Fien Dora
2026-10-27 17:59 ` Junio C Hamano
2026-10-28 20:22 ` Fien Dora
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=20261026132525.45414-1-fiendora5@gmail.com \
--to=fiendora5@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.com \
--cc=siddharthasthana31@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