actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-10 02:53:36 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation
History
dependabot[bot] 62f853cd32
Bump github.com/labstack/echo/v4 in /.automation/test (#3377) 
Bumps [github.com/labstack/echo/v4](https://github.com/labstack/echo) from 4.7.2 to 4.9.0.
- [Release notes](https://github.com/labstack/echo/releases)
- [Changelog](https://github.com/labstack/echo/blob/master/CHANGELOG.md)
- [Commits](https://github.com/labstack/echo/compare/v4.7.2...v4.9.0)

---
updated-dependencies:
- dependency-name: github.com/labstack/echo/v4
  dependency-type: direct:production
...

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

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Lukas Gravley <admiralawkbar@github.com>
2022-10-03 14:03:22 +00:00
..
test Bump github.com/labstack/echo/v4 in /.automation/test (#3377) 2022-10-03 14:03:22 +00:00
clean-code-base-for-tests.sh Inspec additional Tests (#1497) 2021-05-03 16:30:02 -05:00
cleanup-docker.sh Inspec additional Tests (#1497) 2021-05-03 16:30:02 -05:00
README.md switch to main branch (#2010) 2021-10-01 12:57:26 -07:00
upload-docker.sh adding fixes (#1516) 2021-05-04 11:33:21 -05:00
validate-docker-labels.sh Use GitHub Action cache (#1687) 2021-06-24 10:19:42 -05: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.