Skip to content

chore: add AGENTS.md - #2841

Open
cdesiniotis wants to merge 1 commit into
NVIDIA:mainfrom
cdesiniotis:add-agentsmd
Open

chore: add AGENTS.md#2841
cdesiniotis wants to merge 1 commit into
NVIDIA:mainfrom
cdesiniotis:add-agentsmd

Conversation

@cdesiniotis

@cdesiniotis cdesiniotis commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

Description

This PR adds an AGENTS.md file to help AI coding agents contribute to the project. The overall structure of this file takes inspiration from existing projects, namely https://github.com/kubernetes-sigs/dra-driver-nvidia-gpu/blob/main/AGENTS.md. We can definitely fine-tune this file over time.

This addresses SIG-AGT-01, SIG-AGT-13, SIG-AGT-03, SIG-AGT-04, SIG-AGT-05, SIG-AGT-06, SIG-AGT-14, SIG-AGT-15, and SIG-AGT-16. from the OSS Scorecard.

Checklist

  • No secrets, sensitive information, or unrelated changes
  • Lint checks passing (make lint)
  • Generated assets in-sync (make validate-generated-assets)
  • Go mod artifacts in-sync (make validate-modules)
  • Test cases are added for new code paths

Testing

OSS scorecard was run with and without this change.

@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Added AGENTS.md with GPU Operator architecture and directory guidance. It documents build, test, formatting, code generation, manifest validation, Helm, CSV, and notice workflows. It also defines Go conventions, testing practices, contribution requirements, and prohibited practices.

Merge Risk: ⚪ Minimal · up to d1671

This PR only adds contributor guidance; one documented command typo is localized and creates no merge-blocking risk, so it is merge-ready after normal review.


Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Quiet mode is enabled, so only the most important comments were posted inline. Other review comments are grouped below.

🟡 Other comments (1)
AGENTS.md-103-103 (1)

103-103: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Correct the make manifests target name.

Line 103 spells the target as make manifets, so an agent following this instruction will run an invalid Make target. Use the make manifests spelling documented on Line 48.


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: QUIET

Plan: Enterprise

Run ID: 6c15eff0-7dfc-4010-819b-4af1243643bb

📥 Commits

Reviewing files that changed from the base of the PR and between f12acb8 and d167133.

📒 Files selected for processing (1)
  • AGENTS.md

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

Signed-off-by: Christopher Desiniotis <cdesiniotis@nvidia.com>
Comment thread AGENTS.md
- `cmd/` — binary entrypoints (operator manager and CLI tools).
- `deployments/gpu-operator/` — Helm chart for the operator.
- `assets/state-*` — per-operand manifests rendered by the `ClusterPolicy` state manager.
- `manifests/` — per-operand manifests rendered by the `GPUCluster` / `NVIDIADriver ` state managers.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:

Suggested change
- `manifests/` — per-operand manifests rendered by the `GPUCluster` / `NVIDIADriver ` state managers.
- `manifests/` — per-operand manifests rendered by the `GPUCluster` / `NVIDIADriver` state managers.

Comment thread AGENTS.md
# AGENTS.md

Guidance for AI coding agents working in this repository. Human contributors should also read
[CONTRIBUTING.md](CONTRIBUTING.md) and the [documentation site](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/index.html)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Trailing whitespace

There are quite a few in other lines as well (linenumbers: 24, 40, 56, 69, 72, 74, 76, 78, 84, 85, 103, 104)

Comment thread AGENTS.md
## Testing Conventions

- Unit tests are co-located `*_test.go` files using `testify` (`require`/`assert`), typically table-driven
with a `map[string]struct{...}` of cases and `t.Run(name, ...)`. Run via `make unit-test`. New behavior

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of saying New behavior needs a unit test, could we say new Behavior needs appropriate test coverage. I was thinking maybe there are cases where integration tests or end to end tests make more sense than a unit test.

Comment thread AGENTS.md
## Things to avoid

- Never commit credentials, API keys, tokens, passwords, kubeconfigs, or private keys.
- Do not hand-edit generated files. Run `make generate`/`make manifets` to regenerate deepcopy code and

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Do not hand-edit generated files. Run `make generate`/`make manifets` to regenerate deepcopy code and
- Do not hand-edit generated files. Run `make generate`/`make manifests` to regenerate deepcopy code and

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants