mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-09 18:43:34 -05:00
e15a4dc174
test bucket variable Add empty expect words add procjet varaible Add excludes file add patters for urls Add newline at eof Changing lorem ipsum for proper words Add admiralawkbar to expected words Exclude lint templates files Add api apk and ansible as expected words add expected words for cleanup-docker.sh add expected words for ghe-config-apply.sh Fix add-ons spelling Add a bunch new words Simpler url pattern Use common baz word Fix coffeescript spelling Add expected words for ghe-api-config-apply.yml Add ecpected words for linter.sh Fix Multi-line spelling Add more linter.sh expected words Add a whole lot of expected words Add pattern for repeated single char Add space Add expected words for Dockerfile Add more expected words for ghe-api-config-apply.yml Add expected words for he-initial-configuration.yml Add expected words for ghe-ldap-configuration.yml Move spelling/expect -> spelling/allow Set workflow name Fix @admiralawkbar capitalization Fix requirements spelling Add last docker allow words Add last ghe-config-apply allow words Add last linter.sh allow words add last general allow words Add .gitignore allow words Add main.yml allow words Add settings.json.j2 allow words Add empty expect words Test gitignore.txt Fix patter for repeated chars Add some more allowed words more words Add disabling-linters.md allow words commit |
||
|---|---|---|
| .. | ||
| test | ||
| cleanup-docker.sh | ||
| README.md | ||
| upload-docker.sh | ||
.automation
This folder holds automation scripts to help deploy and cleanup DockerHub images of the Super-Linter
cleanup-docker.sh
This script uses GitHub Actions so that when a PR is merged and closed, the GitHub Action is triggered. It will then search DockerHub for the image that was deployed during the development, and remove it.
upload-docker.sh
This script uses GitHub Actions so that when a push to the repository is committed, it will complete the following:
- Checkout the source code
- Build the Docker container for Super-Linter using that source code
- Upload the container to DockerHub
When the script is triggered on master, it will push with the tag:latest which is used by all scripting for general availability. When the script is triggered in a branch, it will push with the tag:NameOfBranch which can be used for:
- testing
- troubleshooting
- debugging
- Note: The branch name will be reduced to alphanumeric for consistency and uploading
test
This folder holds all Test Cases to help run the CI/CT/CD process for the Super-Linter.