Skip to content
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

Update action.yml with find-exec #50

Merged
merged 3 commits into from
Jan 9, 2024
Merged

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Jan 9, 2024

Thank you πŸ™ for your contribution to Ultralytics πŸš€! Your effort in enhancing our repositories is greatly appreciated. To streamline the process and assist us in integrating your Pull Request (PR) effectively, please follow these steps:

  1. Check for Existing Contributions: Before submitting, kindly explore existing PRs to ensure your contribution is unique and complementary.

  2. Link Related Issues: If your PR addresses an open issue, please link it in your submission. This helps us better understand the context and impact of your contribution.

  3. Elaborate Your Changes: Clearly articulate the purpose of your PR. Whether it's a bug fix or a new feature, a detailed description aids in a smoother integration process.

  4. Ultralytics Contributor License Agreement (CLA): To uphold the quality and integrity of our project, we require all contributors to sign the CLA. Please confirm your agreement by commenting below:

    I have read the CLA Document and I hereby sign the CLA

For more detailed guidance and best practices on contributing, refer to our βœ… Contributing Guide. Your adherence to these guidelines ensures a faster and more effective review process.

πŸ› οΈ PR Summary

Made with ❀️ by Ultralytics Actions

🌟 Summary

Enhancement of the Markdown formatting GitHub Action for Ultralytics repositories.

πŸ“Š Key Changes

  • The action to format Markdown files has been modified to use the find command.
  • Specific exclusion of Markdown files in the ./docs directory from formatting.

🎯 Purpose & Impact

  • Purpose: To improve how the repository formats Markdown files, providing more granular control over which files are selected for formatting.
  • Impact: This change prevents the automatic formatting of Markdown files within the ./docs directory, which could be useful to maintain certain formatting specifics in documentation files. Users can expect more consistent and targeted Markdown formatting in the repository, ensuring that docs remain untouched and potentially reducing unexpected changes during auto-formatting processes. πŸ“πŸ› οΈ

@glenn-jocher glenn-jocher merged commit 9c8f0b4 into main Jan 9, 2024
@glenn-jocher glenn-jocher deleted the glenn-jocher-patch-1 branch January 9, 2024 16:55
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.

None yet

2 participants