Labels

When writing Acceptance Tests

When creating Aggregation Services

The base category

When creating frontend base components

When creating brokers to wrap external libraries, resources, services, or APIs

Something isn't working

Creating documentation that outlines your business usiness processes / Standard Operating Procedures

When creating an exposer on a library that others can use

Small change to fix things styling, code formatting, spelling (Not for bug fixes)fixes)

When creating components

Any configuration changes i.e. setting up appsettings.json for your various environments.

When creating an exposer like a REST API

When creating Coordination Services

Creation of a data model (and its migration when EF is used)

Creating documentation has design details for your architecture (High Level Design / Low Level Desig

Improvements or additions to documentation

This issue or pull request already exists

New feature or request

When creating any other kind of exposer i.e. Program.cs

When creating Foundation Services

Good for newcomers

Extra attention is needed

When you are copying code and tests over from another system with no or minor changes like namepsace

Project setup, creating the build project / build scripts

When writing Integration Tests

This doesn't seem right