actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-12-22 23:32:10 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation
History
dependabot[bot] ab5dbb676d
Bump golang.org/x/net from 0.7.0 to 0.17.0 in /.automation/test (#4734) 
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.7.0 to 0.17.0.
- [Commits](https://github.com/golang/net/compare/v0.7.0...v0.17.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Zack Koppert <zkoppert@github.com>
2023-10-15 05:09:19 +00:00
..
test Bump golang.org/x/net from 0.7.0 to 0.17.0 in /.automation/test (#4734) 2023-10-15 05:09:19 +00:00
clean-code-base-for-tests.sh Inspec additional Tests (#1497) 2021-05-03 16:30:02 -05:00
cleanup-docker.sh Follow up with several more documentation and automation renames for the org move from github to super-linter (#4543) 2023-08-17 15:12:11 +00:00
README.md switch to main branch (#2010) 2021-10-01 12:57:26 -07:00
upload-docker.sh Update shellcheck 2023-01-04 01:45:10 -05:00
validate-docker-labels.sh Follow up with several more documentation and automation renames for the org move from github to super-linter (#4543) 2023-08-17 15:12:11 +00: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 the main branch, 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.