epiverse-trace/.github

.github's Issues

Issue in bug report issue template

I believe there is an issue in the bug report issue template which was caused by 81d80ea. The template no longer appears as an option on other Epiverse packages and there is an error message shown when viewing the file on GitHub.

Issue for documentation issue

I think the issue template is missing an entry for documentation issues - which aren't a "bug" as such or a feature request.

Don’t use ${{ }} syntax in the run section

https://github.blog/2023-08-09-four-tips-to-keep-your-github-actions-workflows-secure/#1-dont-use-syntax-in-the-run-section-to-avoid-unexpected-substitution-behavior

Add generic contributing guide available across the epiverse-trace organisation

It could be useful to have a generic contributing guide to use as a default for epiverse-trace package that doesn't need / have a more specific contributing guide.

Examples:

• RStudio default contributing guide, and an example of a more specific contributing guide overwriting it.

Consider adding an activity graph to the org README

Could use:

• https://github.com/herdstat

Exclude RcppExports from linting

This issue is to request that R/RcppExports.R should be excluded from linting as part of the lint-changed-files workflow. The current list aims to exclude unchanged files but also overrides the default exclusion of RcppExports.R, which triggers the line length linter.

I first noticed this issue due to a failing workflow in epiverse-trace/epidemics#135. I missed an earlier instance of this issue in epiverse-trace/epidemics#130 as @bahadzie edited R/RcppExports.R to satisfy the linter, and I ignored the file as it's usually auto-generated.

Pull request template will not work by default

GitHub doesn't implement selection of templates for Pull Requests as for Issues so the current template (as long as it's in a subdirectory) will not be used.

Add issue templates available across the epiverse-trace organisation

linelist provides generic issue templates we might want to re-use. They are already re-used in epiparameters.

https://github.com/epiverse-trace/linelist/tree/main/.github/ISSUE_TEMPLATE

https://github.com/epiverse-trace/linelist/tree/main/.github/PULL_REQUEST_TEMPLATE