mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-22 06:01:05 -05:00
170cabf92b
Some checks failed
Publish Images / Build and Test (push) Has been cancelled
Build and Test / Set build metadata (push) Has been cancelled
Build and Test / Build test suite matrix (push) Has been cancelled
Build and Test / preview-release-notes (push) Has been cancelled
Lint commit / commitlint (push) Has been cancelled
Publish Images / Release (push) Has been cancelled
Build and Test / Build and Test (push) Has been cancelled
Build and Test / Test the Super-linter GitHub Action (push) Has been cancelled
Build and Test / Run test cases (push) Has been cancelled
Build and Test / Check if all the tests passed (push) Has been cancelled
- 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.
36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
<!-- Start with an H2 because GitHub automatically adds the commit description before the template, -->
|
|
<!-- so contributors don't have to manually cut-paste the description after the H1. -->
|
|
<!-- Also, include the header in a "prettier ignore" block because it adds a blank line -->
|
|
<!-- after the markdownlint-disable-next-line directive, making it useless. -->
|
|
<!-- Ref: https://github.com/prettier/prettier/issues/14350 -->
|
|
<!-- Ref: https://github.com/prettier/prettier/issues/10128 -->
|
|
<!-- prettier-ignore-start -->
|
|
<!-- markdownlint-disable-next-line MD041 -->
|
|
## Readiness checklist
|
|
<!-- prettier-ignore-end -->
|
|
|
|
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](https://www.conventionalcommits.org/en/v1.0.0/).
|
|
- [ ] I wrote the necessary upgrade instructions in the
|
|
[upgrade guide](../docs/upgrade-guide.md).
|
|
- [ ] 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.
|