These should be documented at least in the "tool" issue template.
E.g., implicitly I have assumed in a recent refactoring that an issue tracker should have at least one issue, either open or closed, otherwise it does not count. That's because the typical academic code repo on GH comes with an issue tracker by default, but this tracker is not used at all.
These should be documented at least in the "tool" issue template.
E.g., implicitly I have assumed in a recent refactoring that an issue tracker should have at least one issue, either open or closed, otherwise it does not count. That's because the typical academic code repo on GH comes with an issue tracker by default, but this tracker is not used at all.