-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into glenn-jocher-patch-1
- Loading branch information
Showing
5 changed files
with
92 additions
and
114 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Ultralytics 🚀 - AGPL-3.0 license | ||
# Ultralytics Actions https://github.com/ultralytics/actions | ||
# This workflow automatically formats code and documentation in PRs to official Ultralytics standards | ||
|
||
name: Ultralytics Actions | ||
|
||
on: | ||
push: | ||
branches: [main,master] | ||
pull_request: | ||
branches: [main,master] | ||
|
||
jobs: | ||
format: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Run Ultralytics Formatting | ||
uses: ultralytics/actions@main | ||
with: | ||
token: ${{ secrets.GITHUB_TOKEN }} # automatically generated | ||
python: true | ||
docstrings: true | ||
markdown: true | ||
spelling: true | ||
links: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,13 @@ | ||
Thank you 🙏 for your contribution to [Ultralytics](https://ultralytics.com) 🚀! 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: | ||
|
||
<!-- | ||
Thank you 🙏 for submitting a Pull Request to an Ultralytics 🚀 repo! We want to make contributing as possible. A few tips to get you started: | ||
1. **Check for Existing Contributions**: Before submitting, kindly explore existing PRs to ensure your contribution is unique and complementary. | ||
|
||
- Search existing PRs to see if a similar contribution already exists. | ||
- Link this PR to an open Issue to help us understand what bug fix or feature is being implemented. | ||
- Sign the Ultralytics Contributor License Agreement (CLA) by writing the below statement in a PR comment: | ||
I have read the CLA Document and I sign the CLA | ||
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. | ||
|
||
Please see our ✅ [Contributing Guide](https://github.com/ultralytics/ultralytics/blob/master/CONTRIBUTING.md) for more details. | ||
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. | ||
|
||
Note that Copilot will summarize this PR below, do not modify the 'copilot:all' line. | ||
--> | ||
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: | ||
|
||
copilot:all | ||
_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](https://docs.ultralytics.com/help/contributing). Your adherence to these guidelines ensures a faster and more effective review process. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.