Skip to content

Standardize .github configuration - #354

Merged
glenn-jocher merged 1 commit into
mainfrom
github-standardize
Aug 15, 2026
Merged

Standardize .github configuration#354
glenn-jocher merged 1 commit into
mainfrom
github-standardize

Conversation

@glenn-jocher

@glenn-jocher glenn-jocher commented Aug 15, 2026

Copy link
Copy Markdown
Member
  • Restrict the format.yml pull_request trigger to branches: [main], matching the org standard.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Updated the formatting workflow to run on pull request activity targeting main, aligning it with the organization’s standard configuration.

📊 Key Changes

  • Added branches: [main] to the pull_request trigger in .github/workflows/format.yml.
  • Preserved the existing triggers for opened, closed, synchronized, and review-requested pull request events.

🎯 Purpose & Impact

  • Formatting workflow runs only for the specified pull request events when the target branch is main.
  • No user-facing change.

@UltralyticsAssistant UltralyticsAssistant added the devops GitHub Devops or MLops label Aug 15, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. To ensure a seamless integration of your work, please review the following checklist:

  • Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
  • Synchronize with Source: Confirm your PR is synchronized with the ultralytics/docs main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
  • Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
  • Update Documentation: Update the relevant documentation for any new or modified features.
  • Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
  • Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
  • Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

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 UltralyticsAssistant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 PR Review

Made with ❤️ by Ultralytics Actions

Reviewed the .github/workflows/format.yml pull_request trigger and related workflow configuration. Restricting it to the main base branch is consistent with the repository’s existing CI branch filters and does not introduce a concrete regression. LGTM.

@glenn-jocher
glenn-jocher merged commit 176e437 into main Aug 15, 2026
6 checks passed
@glenn-jocher
glenn-jocher deleted the github-standardize branch August 15, 2026 17:30
@UltralyticsAssistant

Copy link
Copy Markdown
Member

🎉 PR #354 has been merged—thank you, @glenn-jocher!

“Great things are done by a series of small things brought together.” — Vincent van Gogh

This focused update aligns the formatting workflow with the organization’s standard configuration by targeting main while preserving the existing pull request events. Great work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devops GitHub Devops or MLops

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants