mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-22 14:10:56 -05:00
e4da77657e
Given the amount of issues due to using outdated versions: - Require users to reproduce issues with the latest Super-linter version. - Remind users to use super-linter/super-linter, and not the deprecated github/super-linter. - Ask contributors to check that CI jobs pass. - Ask maintainers to put a PR in a milestone.
24 lines
1.1 KiB
Markdown
24 lines
1.1 KiB
Markdown
# Proposed changes
|
|
|
|
_describe the proposed changes and remove this template text_
|
|
|
|
## 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](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.
|