Skip to content

Commit 7699489

Browse files
Merge pull request #53 from agentevals-dev/chore/ai-guidelines
Add responsible AI usage guidelines
2 parents 139584d + caf7b4d commit 7699489

3 files changed

Lines changed: 24 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,3 +104,11 @@ body:
104104
attributes:
105105
label: Additional context
106106
description: Anything else that might help (screenshots, related issues, workarounds you tried, etc.).
107+
108+
- type: checkboxes
109+
id: human-check
110+
attributes:
111+
label: Human confirmation
112+
options:
113+
- label: I am a human (not a bot, agent, or AI) filing this issue.
114+
required: true

.github/ISSUE_TEMPLATE/feature_request.yml

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,3 +29,11 @@ body:
2929
attributes:
3030
label: Additional context
3131
description: Anything else (screenshots, links, examples, etc.).
32+
33+
- type: checkboxes
34+
id: human-check
35+
attributes:
36+
label: Human confirmation
37+
options:
38+
- label: I am a human (not a bot, agent, or AI) filing this issue.
39+
required: true

CONTRIBUTING.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,14 @@ The extraction functions in `extraction.py` accept flat `dict[str, Any]` attribu
182182

183183
Each example directory under `examples/` is self-contained with its own `requirements.txt`. The example needs to actually produce OTel spans. For OpenAI-based agents this means including `opentelemetry-instrumentation-openai-v2` in the requirements. Make sure all framework-specific OTel dependencies are listed in the example's `requirements.txt`.
184184

185+
## Responsible AI Usage
186+
187+
We welcome contributors who use AI tools to assist their work, but we ask that you use them responsibly:
188+
189+
- **Do not generate issues, comments, or PR descriptions with AI.** These should be written by you in your own words. Maintainers need to communicate with the person behind the contribution, not a language model.
190+
- **Do not "vibe code."** AI should assist and accelerate code that you (the human!) would write on your own. You are expected to understand every line of code you submit. If you cannot explain a change during review, it will not be merged.
191+
- **Indicate non-trivial AI assistance.** If AI played a significant role in writing your code (beyond autocomplete or minor suggestions), mention it in your PR description. This helps reviewers calibrate their review.
192+
185193
## Getting Help
186194

187195
- Open an [issue](https://github.com/agentevals-dev/agentevals/issues) for bugs or questions

0 commit comments

Comments
 (0)