actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-07 09:45:46 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation
History
Masaya Suzuki e277edca06
Use ts-standard instead of standard as TYPESCRIPT_STANDARD (#2614) 
* Use ts-standard instead of standard as TYPESCRIPT_STANDARD

* Add ts-standard

* Update test case

* Update test case

* Add tsconfig.json

* Add tsconfig.json environment value

* Fix "TypeScript"

* Fix package version

* Fix package version

* Fix package version

* Fix package version

* Fix settings

* Remove config file env

* Fix version

* Fix eslintrc

* Fix project path

* Fix project path

* Fix setting

* Fix env

* Add .eslintrc.yml for ts-standard

* Fix README

* Fix settings

* Change include paths

* Change include paths

* Change include paths

* Change include paths

* Fix dependencies

* Fix dependencies

* Fix dependence versions
2022-03-16 10:21:57 -05:00
..
test Use ts-standard instead of standard as TYPESCRIPT_STANDARD (#2614) 2022-03-16 10:21:57 -05: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.