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

Incomplete bash completion on git commit: --allow-empty-message and --allow-empty

From
HSHadi Safari <hadi@hadisafari.ir>
Date
Aug 16, 2018, 07:46 UTC
Message-ID
<69624916-f6ba-d4a4-e346-69498662905e@hadisafari.ir>
Hi!

I'm wondering why there isn't --allow-empty and --allow-empty-message in completeion list of git commit command. I'm getting only following flags from v2.18.0 on `git commit --`:

--ahead-behind --include --reedit-message= --all --interactive --reset-author --amend --long --reuse-message= --author= --message= --short --branch --no-edit --signoff --cleanup= --no-post-rewrite --squash= --date= --no-verify --status --dry-run --null --template= --edit --only --untracked-files --file= --patch --verbose --fixup= --porcelain --verify --gpg-sign --quiet

Besides, is there any way to allow empty commit message for a repo, e.g. by adding something to `.git/config`? I couldn't find any in docs.

-- 
Hadi
Next: Duy Nguyen
Message 1 of 5 in “Incomplete bash completion on git commit: --allow-empty-message and --allow-empty”
  1. Hadi SafariAug 16, 2018
  2. Duy NguyenAug 16, 2018
  3. completion: include PARSE_OPT_HIDDEN in completion outputÆvar Arnfjörð Bjarmason, Aug 16, 2018
  4. Junio C HamanoAug 16, 2018
  5. Duy NguyenAug 17, 2018

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.