actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-24 23:21:12 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
lint/.automation
History
Marco Ferrari 5a8805dc4f
Exit on errors when running Git (#4889) 
* Exit on errors when running Git

* Skip pulling changes entirely

* Enable pipefail when generating diffs

* Cleanup

* Shallow repo check

* Echo GITHUB_SHA update

* Check if GITHUB_SHA exists before using it

* Move GITHUB_SHA validation to validation script

* Rely on cat-file return code

* Check if DEFAULT_BRANCH exists

* Change dir when checking DEFAULT_BRANCH

* Show git branches

* Don't switch branches

* Check GITHUB_SHA only when needed

* Ensure we have permissions before interacting with the repo

* Remove the DIFF_CMD variable

* Move TEST_CASE_RUN and RUN_LOCAL init up

* Validate if Git repo and if SHA exists

* Move validation function

* Change dir when getting branch names

* Move debug messages up to be less verbose

* Move branch validation in a function

* Fix linting errors
2023-12-04 09:47:49 +00:00
..
test feat: use built-in dotnet format linter for csharp language (#4627) 2023-10-16 18:31:03 +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 Exit on errors when running Git (#4889) 2023-12-04 09:47:49 +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.