This is a super-simple change that moves the linting configuration from the GitHub workflow file to a new .cicd-env file. There are no "real" changes to this package.
[x] This PR does NOT contain PHI or germline genetic data. A repo may need to be deleted if such data is uploaded. Disclosing PHI is a major problem.
[x] This PR does NOT contain molecular files, compressed files, output files such as images (e.g..png, .jpeg), .pdf, .RData, .xlsx, .doc, .ppt, or other non-plain-text files. To automatically exclude such files using a .gitignore file, see here for example.
[x] I have set up or verified the main branch protection rule following the github standards before opening this pull request.
[x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
[ ] I have added the major changes included in this pull request to the NEWS under the next release version or unreleased, and updated the date. I have also updated the version number in DESCRIPTION according to semantic versioning rules.
[ ] Both R CMD build and R CMD check run successfully.
Description
This is a super-simple change that moves the linting configuration from the GitHub workflow file to a new
.cicd-envfile. There are no "real" changes to this package.This change enables the new bllint script from https://github.com/uclahs-cds/docker-CICD-base/pull/60 to lint a checked-out copy of this repository for easier development.
Checklist
[x] This PR does NOT contain PHI or germline genetic data. A repo may need to be deleted if such data is uploaded. Disclosing PHI is a major problem.
[x] This PR does NOT contain molecular files, compressed files, output files such as images (e.g.
.png, .jpeg),.pdf,.RData,.xlsx,.doc,.ppt, or other non-plain-text files. To automatically exclude such files using a .gitignore file, see here for example.[x] I have read the code review guidelines and the code review best practice on GitHub check-list.
[x] I have set up or verified the
mainbranch protection rule following the github standards before opening this pull request.[x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
[ ] I have added the major changes included in this pull request to the
NEWSunder the next release version or unreleased, and updated the date. I have also updated the version number inDESCRIPTIONaccording to semantic versioning rules.[ ] Both
R CMD buildandR CMD checkrun successfully.