There isn't super-linter account on Docker Hub:
https://hub.docker.com/u/super-linter
I think the image should be coming from `ghcr.io/super-linter/super-linter`
Thanks
* move from github org to super-linter org
* rename to super-linter org
* rename to super-linter org
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter and remove dockerhub reference
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rename org to super-linter
* rm dockerhub section link
This adds 4 example files to the local README to do a shared env file.
This is much simpler then adding support directly that I tried in PR #3270.
Fixes: #2851
Add note about `--rm` to remove the container after execution. This should prevent a build up of stopped containers after multiple runs of the super-linter
* switch to main branch
* switch from master to main
* switch default branch to main
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* switch to main branch
* make comment reflect code
* switch to main branch
* Improve wording of LINTER_RULES_PATH docs (#1634).
* Add a template config file for ShellCheck (#1633).
Instruct ShellCheck to search SCRIPTDIR, the directory that the script
being linted is in, for other scripts that are sourced. Otherwise, the
commonly-used source command results in linter error SC1091. See
https://github.com/koalaman/shellcheck/wiki/SC1091 for more details.
* fix line ending
Co-authored-by: Lukas Gravley <admiralawkbar@github.com>
Removed table containing ENV VARS that
could be configured with LINTER_RULES_PATH
from the "Using your own rules files" section.
Added text letting users know that they should
refer to the environment variables table in
the README for a list of filename ENV VARS
Added a "Using your own rules files" section to the
README under the "Template rules" section.
This section may help developers new to super-linter
avoid running into issues #864 and #685.