build: Cupcake #16
build: Cupcake #16
Conversation
Signed-off-by: Michael Vorburger ⛑️ <mike@vorburger.ch>
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
.github/workflows/mega-linter.yaml
Outdated
| # You can override MegaLinter flavor used to have faster performances | ||
| # More info at https://megalinter.io/flavors/ | ||
| uses: oxsecurity/megalinter@b48455a119cc28045eee8f1e9d0a542a85e71f4f # v7.5.0 | ||
| uses: oxsecurity/megalinter/flavors/cupcake@v7.5.0 |
There was a problem hiding this comment.
How does one find the SHA? I can see https://ghcr.io/oxsecurity/megalinter but there's nothing at https://ghcr.io/oxsecurity/megalinter/flavors/cupcake ... @echoix would you happen to know this? (I could contrib an improvement to your docs.)
There was a problem hiding this comment.
Here, in GitHub workflows, the uses: refers to an action, not a docker image. Not all Actions use docker images. So I expect that the sha you are looking for is the commit sha of the tagged release. The flavor is an action file that is in a subdirectory of the repo (as opposed to the one in the root of the repo)
There was a problem hiding this comment.
Oh, je vois! Qu'est ce que j'suis bête... là j'ai compris. Merci bcp, j'apprécie la réponse/clarification - TIL!
* main: build(deps): bump ossf/scorecard-action from 2.0.6 to 2.3.1 Bump actions/checkout from 3.6.0 to 4.1.1 build: Fix Lint problems build: bin/pre-commit build: Skip lychee link checking for *.yaml build: Be!
No description provided.