Labels

Issue or PR documents a breaking change requiring a major version bump.

Issue or PR documents a new feature requiring a minor version bump.

Issue or PR documents a bug fix or enhancement requiring a patch version bump.

Issue or PR is related to RAMSTK dependencies.

Create issue branch when issue is assigned.

Issue or PR is closed as a duplicate of another and both cross-reference one another.

Issue or PR is closed as not valid.

Pull Request has been merged successfully

Issue or PR is closed and will NOT be fixed.

Good issue to get your feet wet...mostly busy work :(

Issue or PR is critical priority; it must be resolved to release.

Issue or PR is high priority.

Issue or PR is low priority.

Issue or PR is normal priority.

Issue has no affect on functionality or quality and requests no new functionality.

Issue or PR tracks next release.

Issue or PR is open, unmilestoned, and unassigned.

Pull Request is complete and integrated or closed for anther reason.

Issue or PR that is requesting user and/or developer feedback.

Issue or PR is open, milestoned, and assigned.

Issue or PR is open, milestoned, assigned, and pull request referenced.

Issue was created automatically from an ISSUE statement in the code.

Issue or PR associated with RAMSTK build system

Issue or PR associated with CI/CD.

Issue or PR is documentation related.

Issue or PR adds or requests new functionality.

Issue or PR affects existing functionality.

Issue or PR dealing with refactoring of RAMSTK code.

Issue or PR affects code quality (e.g., coding standards).

Issue or PR associated with RAMSTK test suite.