Skip to content

Update the readme file according to the changes of the converter scripts in the main repository of ultralytics. #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Hapyr
Copy link

@Hapyr Hapyr commented May 26, 2025

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

No code changes were made in this PR.

📊 Key Changes

  • This PR does not include any updates or modifications to the codebase.

🎯 Purpose & Impact

  • No impact on users or functionality, as there are no changes introduced.
  • May have been opened for administrative, discussion, or placeholder purposes.

@pderrenger
Copy link
Member

Thank you for opening this PR @Hapyr! I see the PR summary indicates no code changes were made, but the title suggests you intended to update the README file to reflect changes in the main Ultralytics repository. Could you please push your README updates so we can review the proposed changes?

@Hapyr
Copy link
Author

Hapyr commented May 27, 2025

@pderrenger I'm not sure if your comments are AI generated, but even if the summary indicates that no code changes have been made, the PR obviously shows that the readme has been edited, wtf?!

@pderrenger
Copy link
Member

@Hapyr You're absolutely right, and I apologize for the confusion. I can clearly see your README updates in the PR - the automated summary was misleading and I should have looked at the actual changes instead of relying on it. Thank you for the clarification and for taking the time to update the documentation to align with the main repository changes.

@kerema14
Copy link

kerema14 commented Jun 7, 2025

why is it still not reviewed?

@pderrenger
Copy link
Member

@kerema14 You're right, this PR needs attention. I'll review @Hapyr's README updates now to get this moving forward - thanks for the reminder.

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.

4 participants