EOVE's organisation-wise configuration files

Creating a new issue

Pick an existing template when possible:

• "Eove bug issue" to report a bug/regression concerning end-user
  • criticity will be evaluated in template
  • production code only (not in test, build script, etc.)
• "Eove feature/enhancement issue" to describe a feature/enhancement for eove products
  • could be a brand-new feature
  • could be a change to an existing feature
  • should concern end-user
• "Eove technical issue" to describe a technical modification
  • could be about a deprecated dependency to update
  • when you detect a lack of test in a feature
  • when we are missing a build script for instance
  • could even be a bug, but in other than production code

Labelling the issue

When issue is created, the template may have applied a label automatically.

If label is missing, pick one among the following list:

• bug:critical: A bug with an accepted risk
• bug:minor: A bug with no risk for the patient
• bug:nc: A bug with an unacceptable risk
• documentation: Improvements or additions to documentation
• feature: A new feature or a change to an existing one
• technical: Far from end-user (refactoring, build, tests)

The exhaustive list is available at Repository labels.

Maintenance

Run prettier from time to time:

npx prettier@3 --write '**/*.{json,md,yml}'