You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I plugged this most excellent of super duper linters into a github action workflow without any alteration. The result failed with the error listed below.
docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "./entrypoint.ps1": stat ./entrypoint.ps1: no such file or directory: unknown.
Reproduce
The github action layout I used was similar to this:
name: 'Run Pull Request Update Checks'on:
pull_request:
types:
- opened
- reopened
- edited
- synchronizedefaults:
run:
shell: pwshworking-directory: .jobs:
github-pr:
name: Lintingruns-on: ubuntu-lateststeps:
- uses: actions/labeler@v2name: Auto Labelwith:
repo-token: "${{ secrets.GITHUB_TOKEN }}"
- uses: aslafy-z/conventional-pr-title-action@mastername: 'Validate Title Adheres to Conventional Commit Format'with:
success-state: Title follows the specification.failure-state: Title does not follow the specification.context-name: conventional-pr-titlepreset: conventional-changelog-angular@latestenv:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}run-linting:
name: 'Apply FMT & Scan For Secrets'runs-on: ubuntu-lateststeps:
- uses: actions/checkout@v2with:
fetch-depth: 0# don't use shallow fetch as I'm trying to commit and push back up changed files to the main# token: ${{ secrets.GITHUB_TOKEN }}
- name: Super Duper Linteruses: JustinGrote/Super-Duper-Linter@preview
The text was updated successfully, but these errors were encountered:
Thanks for the report, it may be a bit before I have time to investigate but I do have it flagged. Keep in mind at the moment this is still "proof of concept" status and not production grade.
Description
I plugged this most excellent of super duper linters into a github action workflow without any alteration. The result failed with the error listed below.
Reproduce
The github action layout I used was similar to this:
The text was updated successfully, but these errors were encountered: