Skip to content

No labels!

There aren’t any labels for this repository quite yet.

26 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
effort: high
effort: high
The issue will probably take a single contributor several days of work to resolve.
4
effort: low
effort: low
The issue will probably take a single contributor no more than one day of work to resolve.
5
effort: moderate
effort: moderate
The issue will probably take a single contributor one or two days of work to resolve.
1
effort: very high
effort: very high
The issue will probably take a single contributor more than a week of work to resolve.
issue: duplicate
issue: duplicate
The issue was closed because it's a duplicate of another issue.
issue: invalid
issue: invalid
The issue was closed because it's inapplicable or doesn't make sense.
issue: question
issue: question
The issue is a question, and it should be closed after the question is answered.
1
issue: wontfix
issue: wontfix
The issue was closed because the relevant changes are not justifiable.
meta: blocked
meta: blocked
The issue cannot be resolved right now, but should be in the future.
meta: good first issue
meta: good first issue
The issue is especially suitable for first-time contributors.
4
meta: needs work
meta: needs work
The issue cannot progress until additional work is done.
meta: next release
meta: next release
The issue must be resolved before the next package version can be released.
3
priority: critical
priority: critical
The issue must be resolved as soon as possible.
1
priority: high
priority: high
The issue substantially impedes people's ability to use the software.
priority: low
priority: low
The issue has only a small impact on people using the software.
4
priority: medium
priority: medium
The issue makes it more difficult for people to use the software.
4
priority: trivial
priority: trivial
The issue has very little impact on people using the software.
1
type: bug
type: bug
The issue involves incorrect or unexpected behavior.
type: code quality
type: code quality
The issue involves code organization and readability.
2
type: documentation
type: documentation
This issue pertains to the clarity or exhaustiveness of package documentation.
3
type: feature
type: feature
The issue involves adding new or extended behavior to the package.
1
type: integration
type: integration
The issue involves interactions with other software.
1
type: optimization
type: optimization
The issue involves making existing functionality more performant.
type: polish
type: polish
The issue involves making existing functionality more usable.
1
type: security
type: security
The issue pertains to security threats and vulnerabilities.
type: stability
type: stability
The issue pertains to automated testing or other tools for verifying code correctness.