DEV Community

Cover image for ISSUE-LABELER: Automated Issue Labeling for GitHub
Dhruv Panchal
Dhruv Panchal

Posted on

1 1

ISSUE-LABELER: Automated Issue Labeling for GitHub

A project submitted for the GitHub + DEV 2023 Hackathon. This tool assists maintainers by extracting labels from the bodies of GitHub issues.

Category Submission

Maintainer Must-Haves

App Link

You can find Issue Labeler here. Want to learn more about how to use Issue Labeler? Check out our Usage Guide.

GitHub logo dhhruv / ISSUE-LABELER

This tool is an aid for open-source maintainers. It is designed to automatically extract labels from GitHub issue descriptions and add them to the issue. This means maintainers do not have to manually label issues, reducing their workload and ensuring that issues are labeled accurately and consistently.

ISSUE-LABELER: Automated Issue Labeling for GitHub

A project submitted for the GitHub + DEV 2023 Hackathon. This tool assists maintainers by extracting labels from the bodies of GitHub issues.

Category Submission

Maintainer Must-Haves

App Link

You can find Issue Labeler here

Description

This tool is an aid for open-source maintainers. It is designed to automatically extract labels from GitHub issue descriptions and add them to the issue. This means maintainers do not have to manually label issues, reducing their workload and ensuring that issues are labeled accurately and consistently.

Screenshots

These screenshots demonstrate the Issue Labeler in action on five different issues. Once each issue is created, the GitHub Actions workflow triggers and the tool starts its work.

  1. First Issue:

    First issue labels

  2. Second Issue:

    Second issue labels

  3. Third Issue:

    Third issue labels

  4. Fourth Issue:

    Fourth issue labels

  5. Fifth Issue:

    Fifth issue labels

Link to Source Code

You can see how we built Issue Labeler by checking out the source code

Background

This project was…

Description

This tool is an aid for open-source maintainers. It is designed to automatically extract labels from GitHub issue descriptions and add them to the issue. This means maintainers do not have to manually label issues, reducing their workload and ensuring that issues are labeled accurately and consistently.

Screenshots

These screenshots demonstrate the Issue Labeler in action on five different issues. Once each issue is created, the GitHub Actions workflow triggers and the tool starts its work.

  1. First Issue:

    First issue labels

  2. Second Issue:

    Second issue labels

  3. Third Issue:

    Third issue labels

  4. Fourth Issue:

    Fourth issue labels

  5. Fifth Issue:

    Fifth issue labels

Link to Source Code

You can see how we built Issue Labeler by checking out the source code

GitHub logo dhhruv / ISSUE-LABELER

This tool is an aid for open-source maintainers. It is designed to automatically extract labels from GitHub issue descriptions and add them to the issue. This means maintainers do not have to manually label issues, reducing their workload and ensuring that issues are labeled accurately and consistently.

ISSUE-LABELER: Automated Issue Labeling for GitHub

A project submitted for the GitHub + DEV 2023 Hackathon. This tool assists maintainers by extracting labels from the bodies of GitHub issues.

Category Submission

Maintainer Must-Haves

App Link

You can find Issue Labeler here

Description

This tool is an aid for open-source maintainers. It is designed to automatically extract labels from GitHub issue descriptions and add them to the issue. This means maintainers do not have to manually label issues, reducing their workload and ensuring that issues are labeled accurately and consistently.

Screenshots

These screenshots demonstrate the Issue Labeler in action on five different issues. Once each issue is created, the GitHub Actions workflow triggers and the tool starts its work.

  1. First Issue:

    First issue labels

  2. Second Issue:

    Second issue labels

  3. Third Issue:

    Third issue labels

  4. Fourth Issue:

    Fourth issue labels

  5. Fifth Issue:

    Fifth issue labels

Link to Source Code

You can see how we built Issue Labeler by checking out the source code

Background

This project was…

Background

This project was inspired by the need to streamline the workflow for open-source maintainers. We observed that labelling issues was a recurring task that could be automated to save maintainers time and effort. We chose to participate in the Maintainer Must-Haves category for the GitHub + DEV 2023 Hackathon, as we believed this was a valuable tool that could assist many maintainers.

How We Built It

We utilized GitHub Actions to create a workflow that triggers whenever a new issue is created. This workflow runs a script that analyzes the issue description and extracts labels based on predefined keywords. The script then adds these labels to the issue.

We also made use of GitHub Codespaces to develop and test our code. This made it easy for our team to collaborate and ensured that we had a consistent development environment.

During the project, we learned a great deal about GitHub Actions and Codespaces, including how to create custom workflows and how to set up a development environment in Codespaces.

Team

Permissive License

This project is licensed under the MIT License - see the LICENSE file for details.

Additional Resources/Info

Want to learn more about how to use Issue Labeler? Check out our Usage Guide. You can also contribute to this project by submitting a pull request or opening an issue on GitHub.

Image of Docusign

🛠️ Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more

Top comments (0)

Sentry image

See why 4M developers consider Sentry, “not bad.”

Fixing code doesn’t have to be the worst part of your day. Learn how Sentry can help.

Learn more

👋 Kindness is contagious

Immerse yourself in a wealth of knowledge with this piece, supported by the inclusive DEV Community—every developer, no matter where they are in their journey, is invited to contribute to our collective wisdom.

A simple “thank you” goes a long way—express your gratitude below in the comments!

Gathering insights enriches our journey on DEV and fortifies our community ties. Did you find this article valuable? Taking a moment to thank the author can have a significant impact.

Okay