ultralytics-actions

🚀 Ultralytics Actions: Auto-Formatting for Python, Markdown, and Swift

Welcome to the Ultralytics Actions repository, your go-to solution for maintaining consistent code quality across Ultralytics Python and Swift projects. This GitHub Action is designed to automate the formatting of Python, Markdown, and Swift files, ensuring adherence to our coding standards.

📄 Actions Description

Ultralytics Actions automatically applies formats, updates, and enhancements:

• Python Code: Using Ruff, a fast Python auto-formatter.
• Markdown Files: With Prettier, ensuring a consistent style in documentation.
• Docstrings: Utilizing docformatter for clean and standardized documentation comments.
• Swift Code: Formatting Swift files using swift-format to ensure consistent coding style across Swift projects. (Requires macos-latest to run correctly.)
• Spell Check: Employing codespell for catching common misspellings.
• Broken Links Check: Implementing Lychee to report broken links in docs and markdown files.
• PR Summary: Generating concise OpenAI GPT4o-powered PR summaries, enhancing PR clarity.
• Auto-labeling: Applying relevant labels to issues and pull requests using OpenAI GPT-4o for intelligent categorization.

🛠 How It Works

Ultralytics Actions triggers on various GitHub events:

• Push Events: Automatically formats code when changes are pushed to the main branch.
• Pull Requests:
  • Ensures that contributions meet our formatting standards before merging.
  • Generates a concise summary of the changes using GPT-4o.
  • Automatically applies relevant labels using GPT-4o for intelligent categorization.
• Issues: Automatically applies relevant labels using GPT-4o when new issues are created.

These actions help maintain code quality, improve documentation clarity, and streamline the review process by providing consistent formatting, informative summaries, and appropriate categorization of issues and pull requests.

🔧 Setting Up the Action

To use this action in your Ultralytics repository:

1. Create a Workflow File: In your repository, create a file under .github/workflows/, e.g., ultralytics-actions.yml.

2. Add the Action: Use the Ultralytics Actions in your workflow file as follows:

   name: Ultralytics Actions
   
   on:
     issues:
       types: [opened]
     pull_request:
       branches: [main]
       types: [opened, closed]
   
   jobs:
     format:
       runs-on: ubuntu-latest
       steps:
         - name: Run Ultralytics Formatting
           uses: ultralytics/actions@main
           with:
             token: ${{ secrets.GITHUB_TOKEN }} # automatically generated, do not modify
             labels: true # autolabel issues and PRs
             python: true # format Python code and docstrings
             prettier: true # format YAML, JSON, Markdown and CSS
             swift: true # format Swift code (requires 'macos-latest')
             spelling: true # check spelling
             links: true # check broken links
             summary: true # print PR summary with GPT4o (requires 'openai_api_key')
             openai_api_key: # your OpenAI API key
   

3. Customize: Adjust the workflow settings as necessary for your project.

💡 Contribute

Ultralytics thrives on community collaboration; we immensely value your involvement! We urge you to peruse our Contributing Guide for detailed insights on how you can participate. Don't forget to share your feedback with us by contributing to our Survey. A heartfelt thank you 🙏 goes out to everyone who has already contributed!

📄 License

Ultralytics presents two distinct licensing paths to accommodate a variety of scenarios:

• AGPL-3.0 License: This official OSI-approved open-source license is perfectly aligned with the goals of students, enthusiasts, and researchers who believe in the virtues of open collaboration and shared wisdom. Details are available in the LICENSE document.
• Enterprise License: Tailored for commercial deployment, this license authorizes the unfettered integration of Ultralytics software and AI models within commercial goods and services, without the copyleft stipulations of AGPL-3.0. Should your use case demand an enterprise solution, direct your inquiries to Ultralytics Licensing.

📮 Contact

For bugs or feature suggestions pertaining to Ultralytics, please lodge an issue via GitHub Issues. You're also invited to participate in our Discord community to engage in discussions and seek advice!