actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-23 06:31:02 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
lint/.github/pull_request-template.md
Marco Ferrari 170cabf92b
Some checks failed
Publish Images / Build and Test (push) Has been cancelled
Details
Build and Test / Set build metadata (push) Has been cancelled
Details
Build and Test / Build test suite matrix (push) Has been cancelled
Details
Build and Test / preview-release-notes (push) Has been cancelled
Details
Lint commit / commitlint (push) Has been cancelled
Details
Publish Images / Release (push) Has been cancelled
Details
Build and Test / Build and Test (push) Has been cancelled
Details
Build and Test / Test the Super-linter GitHub Action (push) Has been cancelled
Details
Build and Test / Run test cases (push) Has been cancelled
Details
Build and Test / Check if all the tests passed (push) Has been cancelled
Details
chore: devcontainer, docs, prettier config (#6119) 
- Update devcontainer by setting Prettier as a formatter only for
  supported languages.
- Install only the VS Code extensions that we need for Super-linter
  development.
- Remove the devcontainer as soon as it's not needed to avoid leaving
  leftovers behind.
- Enable proseWrap in Prettier configuration.
- Update documentation about how to configure new linters.
- Fix linting issues.
2024-09-13 14:37:48 +02:00

1.7 KiB
Raw Permalink Blame History

Readiness checklist

In order to have this pull request merged, complete the following tasks.

Pull request author tasks

  • I checked that all workflows return a success.
  • I included all the needed documentation for this change.
  • I provided the necessary tests.
  • I squashed all the commits into a single commit.
  • I followed the Conventional Commit v1.0.0 spec.
  • I wrote the necessary upgrade instructions in the upgrade guide.
  • If this pull request is about and existing issue, I added the Fix #ISSUE_NUMBER or Close #ISSUE_NUMBER text to the description of the pull request.

Super-linter maintainer tasks

  • Label as breaking if this change breaks compatibility with the previous released version.
  • Label as either: automation, bug, documentation, enhancement, infrastructure.
  • Add the pull request to a milestone, eventually creating one, that matches with the version that release-please proposes in the preview-release-notes CI job.