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

Create tag.yml #80

Merged
merged 1 commit into from
Dec 12, 2024
Merged

Create tag.yml #80

merged 1 commit into from
Dec 12, 2024

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Dec 12, 2024

πŸ› οΈ PR Summary

Made with ❀️ by Ultralytics Actions

🌟 Summary

Added an automated GitHub workflow to streamline tagging and releasing new versions of the repository. πŸš€

πŸ“Š Key Changes

  • New Workflow File (tag.yml): Introduced a GitHub Actions workflow for handling tags and releases.
  • Workflow Dispatch Input: Added inputs for tag_name, publish_tag, and publish_release to allow triggering releases manually.
  • Tag Verification: Checks if a specified tag already exists before publishing.
  • Automated Release Creation: Uses ultralytics-actions to publish a release summary automatically.

🎯 Purpose & Impact

  • Purpose: Simplifies and automates the version management process, ensuring consistent and efficient tagging and releasing practices.
  • Impact: Makes it easier for developers and maintainers to manage releases while providing users with clear version updates and features. ⚑

Signed-off-by: Glenn Jocher <glenn.jocher@ultralytics.com>
@UltralyticsAssistant UltralyticsAssistant added devops GitHub Devops or MLops enhancement New feature or request labels Dec 12, 2024
@UltralyticsAssistant
Copy link
Member

πŸ‘‹ Hello @glenn-jocher, thank you for submitting a yolo-flutter-app πŸš€ PR! 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 and link to any relevant issues. Based on the description you've provided, this PR introduces a tagging and release workflow automationβ€”nice job! πŸŽ‰
  • βœ… Synchronize with Source: Confirm your PR is synchronized with the ultralytics/yolo-flutter-app 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. Please ensure all jobs defined in the tag.yml file run successfully.
  • βœ… Update Documentation: Consider updating the documentation to include details about how contributors can use the new tagging workflow.
  • βœ… Add Tests or Verifications: If testing is required to validate the new workflow (e.g., workflow dispatch testing or verifying edge cases for tag generation), please include those details in your notes or test logs.
  • βœ… Sign the CLA: Ensure you have signed our Contributor License Agreement (CLA) if you haven't yet, by writing "I have read the CLA Document and I sign the CLA" in a new comment.

πŸ’‘ A couple of notes on your PR:

  • The added capability to automate releases using this workflow is a great enhancement for maintaining the repository efficiently! πŸ™Œ
  • For enhanced clarity and safety in the workflow, you might want to confirm if the if condition for the repository and actor correctly restricts workflow execution to your intended use case.

For more guidance, please refer to our Contributing Guide. This is an automated response, but a member of the Ultralytics team will review your PR in more detail soon. Let us know if you have any questions or further updates, and keep up the great work! πŸš€

@glenn-jocher glenn-jocher merged commit bf9ff78 into main Dec 12, 2024
4 checks passed
@glenn-jocher glenn-jocher deleted the glenn-jocher-patch-1 branch December 12, 2024 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops GitHub Devops or MLops enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants