Add Issue Templates and Labels in GitHub repository

Open Beginner friendly
#14,510 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github
Domain
tooling

Research direction

Start by reviewing the repository’s current GitHub issue workflow and the available issue-template and label configuration options. Add templates covering bugs, feature requests, and improvements, plus the requested status labels, with prompts for version, operating system, reproduction details, and consistent formatting; done means new reports collect this information and labels clarify their status.

Written by the indexing model from the issue text.

Description

I'd like to suggest adding a GitHub issue template for this repository, as well as labels.
I think this will improve the clarity and quality of the reports.

A title starting with “Bug”, “Future Request” or “Improvement” + a label makes it easier to understand what the issue is about, since the title isn’t always clear enough on its own.

For example: Bug – a problem with the program.
Future Request – a request to add a new feature.
Improvement – a request to expand or improve an existing feature.

A template can also help users provide all the required information when submitting a request, without the need to individually ask about and request additional details.

Information such as the version of the software being used, the operating system, and instructions on how the description of such a report should be structured and how detailed it should be—along with consistent formatting—makes it easier to read and allows issues to be reviewed and verified more efficiently.

It would also be a good idea to add some additional labels, such as “approved” or “planned,” so that it's clear the request has been accepted and will be implemented in the future.

Dominant language
C#
Stars
14.3k
Forks
1.3k
Avg merge
1h 19m
Merged PRs (30d)
782

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SubtitleEdit/subtitleedit

All issues in SubtitleEdit/subtitleedit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.