Labels

Issues resulting from a code or process audit

Work that needs to be done sometime in the future. No milestone assigned or not yet available.

Further development work cannot be done.

An error that causes the feature to behave differently than what was expected based on design.

Issue/PR closed without resolution.

Feature that impacts the CLI tool

Issue/PR was resolved (work was done/merged).

Issue declined and will not be worked.

Pull requests that update a dependency file

Issue/PR for feature design documents.

Feature that impacts docker

Duplicates an existing issue either directly or indirectly.

A body of work that can be broken down into specific tasks.

An issue found after the feature was completed, but caught in a testing env prior to a prod release.

Enhancing an existing feature driven by business requirements. Typically backwards compatible.

Pull requests that update Github Actions code.

Issues which are ideal for a first time or new project contributor.

Issues that can become a “good first issue” but need more description/context.

Issues highlighted by lists for Hacktoberfest (https://hacktoberfest.com/)

Pull Requests counted for Hacktoberfest (https://hacktoberfest.com/)

Code changes driven by non business requirements.

Pull requests that update Javascript code

Further development work cannot be done.

A new feature, service, or documentation. Major changes that are not backwards compatible.

Issues that can be solved without coding like documentation.

Not resolvable due to the inability to reproduce the reported issue.

An issue impacting production environments or impacting multiple releases or multiple individuals.

High priority issue, which must be completed in the milestone otherwise the release is at risk.

Required to be completed in the assigned milestone, but may or may not impact the release schedule.