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

Re: [Outreachy] Question about check-ref-format test coverage

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Oct 24, 2026, 09:52 UTC
Message-ID
<bd00b525-6e05-4c17-91ef-3d9c80ff2784@gmail.com>
In-Reply-To
<CAHwyqnXEC7cFijGWATqfA+fBcn09UoNPBDA17GYEY4P8mS0fWA@mail.gmail.com>
On 23/10/2026 16:53, Harald Nordgren wrote:
Show 11 quoted lines
>>
>> ./git check-ref-format --allow-onelevel foo
>>
>> ./git check-ref-format --allow-onelevel --no-allow-onelevel foo
>>
>> it returned with an exit code of 0 and 1 respectively.
> > `--allow-onelevel´ and ´--no-allow-onelevel´ are contradictory
> options, and shouldn't be run together, so that's likely why it failed
> with exit code 1.
>
> This is true for any `--xyz´ and ´--no-xyz´ options.
Our commands allow "--no-xyz" to override "--xyz" which is useful when an alias includes "--xyz" and you want to use the alias without that option. The second command above exits 1 because "foo" is a one-level ref and we've passed "--no-allow-onelevel" which overrides the earlier "--allow-onelevel"
Thanks
Phillip
Previous: Harald NordgrenNext: Fien Dora
Message 3 of 5 in “[Outreachy] Question about check-ref-format test coverage”
  1. Fien DoraOct 23, 2026
  2. Harald NordgrenOct 23, 2026
  3. Phillip WoodOct 24, 2026
  4. Fien DoraOct 24, 2026
  5. Phillip WoodOct 24, 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.