Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] gitignore: ignore ltp-agent setup files
Date: Sat, 30 May 2026 09:22:49 +0000	[thread overview]
Message-ID: <20260530092250.4062-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260530-gitignore_ltp_agent-v1-1-e8812d8de8c5@suse.com>

Hi Andrea,

Thank you for the patch.

> gitignore: ignore ltp-agent setup files
>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>

The commit message is missing a body. Please add a brief explanation of
what these entries are and why they need to be ignored — e.g. that they
are files and symlinks injected at runtime by the ltp-agent tool into
the LTP working directory, and must not be tracked or committed.

> +# ltp-agent setup
> +AGENTS.md
> +GEMINI.md
> +.agents
> +.claude
> +agents
> +linter
> +skills

The `linter` entry is problematic. The upstream LTP repository tracks a
`linter/` directory containing the `ltp-linter` script. In a normal LTP
checkout, adding `linter` (without a leading `/`) to `.gitignore` will
silently suppress any new, untracked files a developer adds to that
directory from appearing in `git status`. This can easily cause
work-in-progress changes to the linter to go unnoticed.

Use an anchored, directory-specific pattern to limit the match to the
ltp-agent-injected symlink at the repository root:

  /linter/

The same logic applies to `agents` and `skills`: prefer anchored
patterns (`/agents/`, `/skills/`) so they only match at the root and
cannot accidentally shadow tracked subtrees in the future.

The remaining entries (AGENTS.md, GEMINI.md, .agents, .claude) are
fine as-is since they are specific enough not to conflict with anything
currently tracked in LTP.

Overall: Needs revision ✗

---
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-05-30  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30  7:32 [LTP] [PATCH] gitignore: ignore ltp-agent setup files Andrea Cervesato
2026-05-30  9:22 ` linuxtestproject.agent [this message]
2026-06-03 21:22 ` Jan Stancek via ltp
2026-06-05  7:07   ` Andrea Cervesato via ltp
  -- strict thread matches above, loose matches on Subject: below --
2026-06-01  6:42 [LTP] [PATCH v2] " Andrea Cervesato
2026-06-01  9:37 ` [LTP] " linuxtestproject.agent
2026-06-01  6:46 [LTP] [PATCH v3] " Andrea Cervesato
2026-06-01  9:39 ` [LTP] " linuxtestproject.agent

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=20260530092250.4062-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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