Add GitHub Models automation workflows #6560
Conversation
- Auto-assign issues to contributors - Welcome first-time contributors - Detect duplicate issues - Flag PRs with unrelated changes Implements commons-app#6547
nicolas-raoul
left a comment
nicolas-raoul
left a comment
There was a problem hiding this comment.
Could you replace all occurrences of "PR" with "pull request"? Full words are cheap, unambiguous and newbie-friendly. 🙂
|
Changes made as requested - replaced all instances of 'PR' with 'pull request' and updated the guidelines text. Thanks for the feedback! |
| Write a friendly welcome message for a first-time contributor. Include: | ||
| 1. Thank them for their first PR | ||
| 2. Mention checking CONTRIBUTING.md | ||
| 3. Explain that after fixing 5 bugs, they can work on enhancements |
There was a problem hiding this comment.
@nicolas-raoul Should this be "Features" instead of enhancements, as we migrated all the issues with label: enhancement to type: Feature ?
There was a problem hiding this comment.
Great point @Kota-Jagadeesh !
"feature" is a bit more ambiguous than "enhancement" so I would suggest the wording "adding features".
By the way, the same probably applies to our documentation too. 🙂
There was a problem hiding this comment.
Great point @Kota-Jagadeesh !
"feature" is a bit more ambiguous than "enhancement" so I would suggest the wording "adding features".
By the way, the same probably applies to our documentation too. 🙂
Yep, will fix the documentation :)
| if: steps.check-request.outputs.response == 'yes' | ||
| uses: actions/github-script@v7 | ||
| with: | ||
| script: | |
There was a problem hiding this comment.
Sorry: do we first check whether the issue is assigned already? Sometimes a volunteer asks to be assigned to an issue that has already be assigned to someone else a few hours ago. In such cases we kindly ask them to find another bug and give them the issue search link found in the Welcome page. It would be fantastic to automate that. 🙂
| Write a friendly welcome message for a first-time contributor. Include: | ||
| 1. Thank them for their first PR | ||
| 2. Mention checking CONTRIBUTING.md | ||
| 3. Explain that after fixing 5 bugs, they can work on enhancements |
There was a problem hiding this comment.
Great point @Kota-Jagadeesh !
"feature" is a bit more ambiguous than "enhancement" so I would suggest the wording "adding features".
By the way, the same probably applies to our documentation too. 🙂
…ancements' to 'adding features'
|
Changes made as requested - check for already assigned issues, and changed 'enhancements' to 'adding features' |
|
I tested, it reported that your PR is within the scope of the issue :) Could you please check the warning and modify the inputs according to the latest ones mentioned docs? 
Also, I have enabled both GPT-4o mini and gpt-5-mini for now, we can revisit later. 
|
|
✅ Generated APK variants! |
…/apps-android-commons into github-models-integration
4 participants
Implements #6547
What changes did you make and why?
This PR adds four GitHub Models automation workflows to help with repository maintenance:
auto_assign.yml) - Assigns issues to contributors who request them, checking they don't have incomplete workwelcome_new_contributors.yml) - Greets first-time contributors with guidelines about the 5 bugfixes rule and links to documentationsuggest_duplicate_bug.yml) - Automatically suggests possible duplicates when new issues are openedpull_request_unrelated_changes.yml) - Reminds contributors to keep PRs focused per CONTRIBUTING.md guidelinesAll workflows use GitHub Models' free tier which has sufficient rate limits for this project's needs.
Tests performed
These are GitHub Actions workflows that will run automatically when triggered. They cannot be fully tested until merged, but:
Screenshots
These are automation workflows with no UI changes.