Labels
Labels
30 labels
- Pull requests that update .net code
- New tickets that need to be hashed out a bit more before they hit the backlog.
- Where tickets start after being triaged. This means the ticket has targeted milestone/labels.
- Waiting on a response from either a commenter or ticket creator.
- Tickets that are on deck/assigned. All ready to go.
- Tickets that are currently being worked on.
- This is for tickets that need to be reviewed prior to being complete.
- Tickets that have been completed and are ready for release.
- The area addressed in the ticket has been released in the product and is generally available.
- Issues that are blocked by something external to the code base.
- A breaking change requires a major version bump (pre v1 does not apply in the same way).
- Tickets that represent defects/bugs.
- Issues and Tasks related to build automation.
- Pull requests that update a dependency file
- This issue requires a change to documentation.
- Issues that are duplicates.
- Enhancements are things that are improvements or features.
- Pull requests that update GitHub Actions code
- This issue is a giood issue to work on for Hacktoberfest.
- This issue / pull request has been accepted as part of Hacktoberfest.
- This is used to mark Hacktoberfest pull requests as invalid
- Tickets related to things that are invalid or are unable to be reproduced.
- Should not be included in the release notes - not enhancing or fixing end product.
- Issues that have had no updates and cannot be progressed.
- Represents high priority tickets - things that must be addressed soon.
- Represents tickets that are of lower priority and can be taken care of whenever.
- Related to security in some way. Much of what we do is centered around security and this is higher.
- Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
- Issues related to the tests (NUnit or Pester)
- A ticket tied to the wrong repository would receive this label.