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

[Feature Request]: Add: "auto-label" GitHub Workflow for Automated Labeling #76

Closed
4 tasks done
samyak-aditya opened this issue Oct 12, 2024 · 2 comments · Fixed by #77
Closed
4 tasks done

[Feature Request]: Add: "auto-label" GitHub Workflow for Automated Labeling #76

samyak-aditya opened this issue Oct 12, 2024 · 2 comments · Fixed by #77
Assignees

Comments

@samyak-aditya
Copy link
Contributor

samyak-aditya commented Oct 12, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Feature Description

Objective: Implement an "auto-label" GitHub workflow to automatically assign the "gssoc-ext" and "hacktoberfest-accepted" labels to relevant pull requests and issues.

Use Case

Details:

  • This workflow will streamline the labeling process by automatically applying the "gssoc-ext" and the "hacktoberfest-accepted" label to Issues.
  • By automating these labels, we can ensure consistent tracking and visibility of contributions tied to these significant events.

Benefits

Implementing this "auto-label" workflow will enhance project organization

Add ScreenShots

No response

Priority

High

Record

  • I have read the Contributing Guidelines
  • I'm a GSSOC'24 contributor
  • I have starred the repository

hey @Soujanya2004 Please Assign it to me with label "gssoc-ext" , "hacktoberfest-accepted" and "level3"

@samyak-aditya
Copy link
Contributor Author

hey @Soujanya2004 Please Assign it to me with label "gssoc-ext" , "hacktoberfest-accepted" and "level3"

@samyak-aditya
Copy link
Contributor Author

Hey @Soujanya2004 I have created the pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants