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

Add GitHub Actions for Automated Labeling and Triage of PRs and Issues #1041

Open
krapie opened this issue Oct 19, 2024 · 0 comments
Open

Add GitHub Actions for Automated Labeling and Triage of PRs and Issues #1041

krapie opened this issue Oct 19, 2024 · 0 comments
Labels
enhancement 🌟 New feature or request

Comments

@krapie
Copy link
Member

krapie commented Oct 19, 2024

Description:

I propose the addition of GitHub Actions to automatically triage, label, and assign pull requests (PRs) and issues across all repositories in the yorkie-team organization. This functionality is essential for effectively tracking all issues and PRs and will significantly enhance our workflow.

Additionally, I recommend implementing a feature that automatically assigns labels when team members create PRs or issues. This capability will be especially useful during the Open Source Contribution Academy (OSSCA), where mentees will be associated with OSSCA team members. The automated labeling will allow us to monitor and gather metrics related to OSSCA activities more effectively.

Why:

With the increase in contributions and activities across the organization, the automation of labeling and triaging will streamline the management process. It will improve visibility into ongoing contributions and ensure that we can effectively track the progress and engagement during OSSCA, ultimately fostering a more organized and efficient open-source contribution environment.

@krapie krapie added the enhancement 🌟 New feature or request label Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🌟 New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant