[GH-ISSUE #262] ignore_prompts: true does not exclude prompts #96

New issue

Closed

opened 2026-03-02 04:11:47 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 04:11:47 +03:00

Owner

Originally created by @franklhs on GitHub (Dec 4, 2025).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/262

Following the readme and set ignore_prompts: true

cat ~/.git-ai/config.json
{
  "git_path": "/usr/bin/git",
  "ignore_prompts": true
}

However, git notes --ref=ai show <commit_hash> still shows all the prompts and messages.

Originally created by @franklhs on GitHub (Dec 4, 2025). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/262 Following the readme and set `ignore_prompts: true` ``` cat ~/.git-ai/config.json { "git_path": "/usr/bin/git", "ignore_prompts": true } ``` However, `git notes --ref=ai show <commit_hash>` still shows all the prompts and messages.

kerem closed this issue

2026-03-02 04:11:47 +03:00

kerem commented

2026-03-02 04:11:48 +03:00

Author

Owner

@svarlamov commented on GitHub (Dec 4, 2025):

Thank you so much for this report, @franklhs! This was indeed a regression that was introduced recently by mistake during a large refactor. We've reimplemented the functionality, added a new testing harness to support config change testing, and added a suite of regression tests for ignore_prompts that will prevent this bug from being reintroduced in the future. Please run git-ai upgrade to get the latest release where this bug has been fixed (1.0.22 / )

@svarlamov commented on GitHub (Dec 4, 2025): Thank you so much for this report, @franklhs! This was indeed a regression that was introduced recently by mistake during a large refactor. We've reimplemented the functionality, added a new testing harness to support config change testing, and added a suite of regression tests for `ignore_prompts` that will prevent this bug from being reintroduced in the future. Please run `git-ai upgrade` to get the latest release where this bug has been fixed (`1.0.22` / )

kerem referenced this issue

2026-03-02 04:13:57 +03:00

[PR #547] fix: show working log output in production mode when --show-working-log flag is provided #552