You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked "open" and "closed" issues, and this is not a duplicate.
Problem or Missing Functionality
I would like to request the addition of an auto-label workflow in this repository to automatically label pull requests with "gssoc-ext" and "hacktoberfest-accepted" during relevant events such as GSSoC (GirlScript Summer of Code) and Hacktoberfest.
Feature Description
Key Features:
Auto-label on PR Creation:
Automatically apply the "gssoc-ext" label for any pull requests submitted as part of GSSoC.
Automatically apply the "hacktoberfest-accepted" label for pull requests during the Hacktoberfest period, or when contributors indicate Hacktoberfest participation.
Workflow Automation:
Use GitHub Actions to create a workflow that triggers upon pull request creation, checking the event or time period, and assigning the appropriate label automatically.
Custom Conditions:
Allow maintainers to manually override the labels if necessary.
Include a check to ensure only valid PRs contributing to the project are labeled with "hacktoberfest-accepted", following Hacktoberfest rules.
Benefits:
Efficiency: Automating this process will save time for maintainers by reducing manual labeling.
Transparency: Ensures that contributors clearly know when their pull request has been accepted for relevant events.
Compliance: Helps in staying aligned with the official rules for Hacktoberfest, where labels like "hacktoberfest-accepted" are required to validate contributions.
Suggested Implementation:
Add a GitHub Actions workflow file in .github/workflows that triggers on pull request events and applies the labels based on specific conditions.
Screenshots
No response
Would you like to work on this feature?
Yes
Implementation Plan
No response
The text was updated successfully, but these errors were encountered:
👋 Thank you @souvikpramanikgit for raising an issue! We’re thrilled to have your input as we work to make this project even better. Our team will review it shortly, so stay tuned! Meanwhile, make sure your issue gets noticed, don’t forget to star the repo 🌟 and follow @ajaynegi45 for even more project insights!
Is this feature already requested?
Problem or Missing Functionality
I would like to request the addition of an auto-label workflow in this repository to automatically label pull requests with "gssoc-ext" and "hacktoberfest-accepted" during relevant events such as GSSoC (GirlScript Summer of Code) and Hacktoberfest.
Feature Description
Key Features:
Auto-label on PR Creation:
Automatically apply the "gssoc-ext" label for any pull requests submitted as part of GSSoC.
Automatically apply the "hacktoberfest-accepted" label for pull requests during the Hacktoberfest period, or when contributors indicate Hacktoberfest participation.
Workflow Automation:
Use GitHub Actions to create a workflow that triggers upon pull request creation, checking the event or time period, and assigning the appropriate label automatically.
Custom Conditions:
Allow maintainers to manually override the labels if necessary.
Include a check to ensure only valid PRs contributing to the project are labeled with "hacktoberfest-accepted", following Hacktoberfest rules.
Benefits:
Efficiency: Automating this process will save time for maintainers by reducing manual labeling.
Transparency: Ensures that contributors clearly know when their pull request has been accepted for relevant events.
Compliance: Helps in staying aligned with the official rules for Hacktoberfest, where labels like "hacktoberfest-accepted" are required to validate contributions.
Suggested Implementation:
Add a GitHub Actions workflow file in .github/workflows that triggers on pull request events and applies the labels based on specific conditions.
Screenshots
No response
Would you like to work on this feature?
Yes
Implementation Plan
No response
The text was updated successfully, but these errors were encountered: