actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-22 14:10:56 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
lint/.automation
History
dependabot[bot] b2491c3bd6
Bump pylint from 2.7.0 to 2.7.1 in /dependencies (#1256) 
* Bump pylint from 2.7.0 to 2.7.1 in /dependencies

Bumps [pylint](https://github.com/PyCQA/pylint) from 2.7.0 to 2.7.1.
- [Release notes](https://github.com/PyCQA/pylint/releases)
- [Changelog](https://github.com/PyCQA/pylint/blob/master/ChangeLog)
- [Commits](https://github.com/PyCQA/pylint/compare/pylint-2.7.0...pylint-2.7.1)

Signed-off-by: dependabot[bot] <support@github.com>

* fix jscpd

* fix json

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Admiral Awkbar <admiralawkbar@github.com>
2021-02-24 09:09:56 -06:00
..
test Bump pylint from 2.7.0 to 2.7.1 in /dependencies (#1256) 2021-02-24 09:09:56 -06:00
clean-code-base-for-tests.sh Use git ls-tree to build file list (#1192) 2021-02-23 11:51:34 -06:00
cleanup-docker.sh break out: (#990) 2020-11-12 11:27:34 -06:00
README.md Format Markdown 2020-07-21 12:08:05 -05:00
trivy-security-scan.sh only show high and critical (#1229) 2021-02-18 10:21:53 -06:00
upload-docker.sh break out: (#990) 2020-11-12 11:27:34 -06:00
validate-docker-labels.sh Try to build with caching to help build times (#1051) 2020-12-04 12:49:09 -06:00

README.md

.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.