epiverse-trace / epiverse-trace/finalsize
Temporarily disable backport linter
Open
- Dominant language
- R
- Stars
- 15
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
This issue is to flag that {lintr} throws confusing warnings from the backport linter when encountering a dependency on R >= 2.10, which causes the lint-changed-files workflow to fail.
This is temporarily fixed by
- [x] Disabling the backport linter in `.lintr`
- [ ] Re-enabling backport linter in `.lintr` once {lintr} issue is fixed
Contributor guide
Research direction
Read `.lintr` and inspect the `lint-changed-files` workflow to understand the disabled backport linter. Check whether the {lintr} dependency warning is fixed; done means re-enabling the linter in `.lintr` without causing the workflow to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, r
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100