Align AGENTS.md with canonical Core Principles and PR Workflow - #142
Conversation
|
👋 Hello @glenn-jocher, thank you for submitting a
For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀 |
UltralyticsAssistant
left a comment
There was a problem hiding this comment.
🔍 PR Review
Made with ❤️ by Ultralytics Actions
Clean PR. The AGENTS.md updates match the provided canonical principles and workflow, and the README clarification accurately reflects the converter behavior: LabelMe writes data.yaml, while COCO writes a YAML named after each input JSON file.
|
🎉 Thank you, @glenn-jocher, and congratulations on the merge!
This PR makes it easier for contributors to get started with clear, focused guidance while documenting the different YAML outputs for LabelMe and COCO conversions. These thoughtful documentation improvements reduce confusion, support cleaner contributions, and help everyone work more effectively. We truly appreciate your contribution! |
AGENTS.mdstill carried an older four-principle Core Principles block and a four-step PR Workflow that named the Codex CLI specifically. Replaced both with the canonical Ultralytics text shared across the org; the repo-specific Commands, Architecture, and Conventions sections are unchanged.data.yaml. Onlyconvert_labelme_json()does;convert_coco_json()writes one<json-stem>.yamlof class names per input file (write_coco_yaml). Noted inline.🛠️ PR Summary
Made with ❤️ by Ultralytics Actions
🌟 Summary
Clarifies repository contribution guidance and documents LabelMe versus COCO output YAML behavior. 📝
📊 Key Changes
AGENTS.mdto emphasize simple, owner-focused fixes, reuse of existing code, minimal scope, and zero-regression validation.README.mdto explain that:data.yaml.<json-stem>.yamlclass-name file per input JSON.🎯 Purpose & Impact