Skip to content

Latest commit

 

History

History
19 lines (12 loc) · 919 Bytes

File metadata and controls

19 lines (12 loc) · 919 Bytes

Contributing to eLabFTW

Please see the documentation.

Issue triage

In order to help organize issues, correct tags must be applied to new issues.

How to best label new issues:

  • Is it a bug or a feature? Adjust tags if needed.
  • Is it a duplicate? Close it using the "close as duplicate" feature of GitHub, pointing to the older issue.
  • Is it reproducible? If it is reproducible, add the tag "reproducible", maybe a "priority:" tag, too. Otherwise, ask for more information and add the tags "not reproducible" and "more info required".
  • What module is this related to? Add the corresponding "module:" tag if a pertinent tag exists.

Then answer:

  • For bugs: write a brief message explaining whether it's reproducible or not.
  • For feature requests, simply acknowledge the request with a generic message: "Thank you for your request, we will look into it".