Add CONTRIBUTING.md, AGENTS.md#299
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Jakob-Naucke The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Reviewer's GuideAdds project contribution and agent-usage guidelines, wires them into the repo, and refines the README repository structure section to better describe Rust-based operator components and supporting crates. File-Level Changes
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
| .await?; | ||
| ``` | ||
| - When functionality is changed, perform `make test` and [integration test](./tests/README.md) at least with basic attestation. | ||
| - Prepend your commit subject with a short focus area. Omit this when making general operator changes. Examples are `tests`, `tests/azure`, `rvs` (reference values) |
There was a problem hiding this comment.
Open to fix, feat also being a prefix, but IMO it should still mention the focus area (when it isn't all-operator), e.g. fix:tests: …
There was a problem hiding this comment.
Hey - I've found 3 issues, and left some high level feedback:
- The README anchor link in AGENTS.md (
./README.md##trusted-execution-cluster-operator-trusted-cluster-operator) looks malformed (double#); consider correcting it to the actual section ID so navigation works. - In AGENTS.md, the line
and agents should suggest when they detectis a sentence fragment; consider rephrasing or completing it to make the guidance clearer. - The new
.cursor/rules/project.mdcfile is added but empty in the diff; consider either removing it from the repo or populating it with the intended rules to avoid committing an unused config stub.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The README anchor link in AGENTS.md (`./README.md##trusted-execution-cluster-operator-trusted-cluster-operator`) looks malformed (double `#`); consider correcting it to the actual section ID so navigation works.
- In AGENTS.md, the line `and agents should suggest when they detect` is a sentence fragment; consider rephrasing or completing it to make the guidance clearer.
- The new `.cursor/rules/project.mdc` file is added but empty in the diff; consider either removing it from the repo or populating it with the intended rules to avoid committing an unused config stub.
## Individual Comments
### Comment 1
<location path="README.md" line_range="22-24" />
<code_context>
+### Other crates
+
- `/lib`: Shared Rust definitions, including translated CRDs
+- `/tests`: Non-unit tests, most rely on a cluster being available. Many of those also rely on a virtualization backend.
+- `/test_utils`: Operator setup helpers and virtualization backends
+
</code_context>
<issue_to_address>
**suggestion (typo):** Consider fixing the comma splice in the `/tests` description for grammatical correctness.
The sentence "Non-unit tests, most rely on a cluster being available." is a comma splice. Consider revising to "Non-unit tests; most rely on a cluster being available." or "Non-unit tests. Most rely on a cluster being available."
```suggestion
### Other crates
- `/lib`: Shared Rust definitions, including translated CRDs
- `/tests`: Non-unit tests; most rely on a cluster being available. Many of those also rely on a virtualization backend.
- `/test_utils`: Operator setup helpers and virtualization backends
```
</issue_to_address>
### Comment 2
<location path="AGENTS.md" line_range="3" />
<code_context>
+# Project objective
+
+See [README](./README.md##trusted-execution-cluster-operator-trusted-cluster-operator).
+
+- **Success looks like**: With the operator deployed, all nodes in the cluster are attested from hardware to software.
</code_context>
<issue_to_address>
**issue (bug_risk):** The README link fragment appears to have an extra `#`, which may break the anchor.
The link path uses `README.md##...`, but section anchors should use a single `#` (e.g. `README.md#section-name`). Please adjust the fragment so it matches the actual heading and the link resolves correctly.
</issue_to_address>
### Comment 3
<location path="CONTRIBUTING.md" line_range="25" />
<code_context>
+)
+.await?;
+```
+- When functionality is changed, perform `make test` and [integration test](./tests/README.md) at least with basic attestation.
+- Prepend your commit subject with a short focus area. Omit this when making general operator changes. Examples are `tests`, `tests/azure`, `rvs` (reference values)
</code_context>
<issue_to_address>
**suggestion (typo):** The phrase "and [integration test]" is missing an article and reads slightly ungrammatically.
You could rephrase to "perform `make test` and an [integration test]" or "perform `make test` and the [integration tests]" so the sentence is grammatically complete.
```suggestion
- When functionality is changed, perform `make test` and an [integration test](./tests/README.md) at least with basic attestation.
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| ) | ||
| .await?; | ||
| ``` | ||
| - When functionality is changed, perform `make test` and [integration test](./tests/README.md) at least with basic attestation. |
There was a problem hiding this comment.
suggestion (typo): The phrase "and [integration test]" is missing an article and reads slightly ungrammatically.
You could rephrase to "perform make test and an [integration test]" or "perform make test and the [integration tests]" so the sentence is grammatically complete.
| - When functionality is changed, perform `make test` and [integration test](./tests/README.md) at least with basic attestation. | |
| - When functionality is changed, perform `make test` and an [integration test](./tests/README.md) at least with basic attestation. |
and links to those from some tools we use, and some README updates with it Signed-off-by: Jakob Naucke <jnaucke@redhat.com>
and links to those from some tools we use, and some README updates with it
Summary by Sourcery
Document contribution guidelines and agent usage conventions and link them from the main project documentation.
Documentation:
Chores: