nextcloud / nextcloud/passman

Use GitHub's issue templates to select a bug or a feature request

Open
#634 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
823
Forks
117
Avg merge
1d 21h
Merged PRs (30d)
8

Description

Feature request

User type: n/a

User level: n/a

Description

Use GitHub's issue templates for bugs and feature requests.

For information, see https://help.github.com/en/github/building-a-strong-community/about-issue-and-pull-request-templates

For a guide on how to set it up for this repo, see https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

Benefit / value

This is the de-facto way to add templates for issues and PRs. Having text in the issue for both an issue and feature request, then having to remove one chunk of text is confusing.

Risk / caveats

Risks will lessen because the required text in issues should always be appropriate.

Sponsorship

None

Are you a developer willing to implement this feature?: No (need privileges to the repo to set this up)

Can you sponsor the development of this feature or do you know someone who can?: No (it's not a significant amount of work)


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Open the contributing guide

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.

Research direction

Start with GitHub's issue-template documentation and the repository's template chooser configuration described in the linked setup guide. Done means contributors can select separate bug and feature-request templates without removing one template from the other.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.