mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-25 10:10:56 -05:00
170cabf92b
- 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.
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
# Contributing
|
|
|
|
:wave: Hi there!
|
|
|
|
We're thrilled that you'd like to contribute to this project. Your help is
|
|
essential for keeping it great.
|
|
|
|
## Submitting a pull request
|
|
|
|
We use [pull requests](https://github.com/super-linter/super-linter/pulls) to
|
|
contribute new features, fixes, or documentation.
|
|
|
|
Here are a few things you can do that will increase the likelihood of your pull
|
|
request being accepted:
|
|
|
|
- Keep your change as focused as possible. If there are multiple changes you
|
|
would like to make that are not dependent upon each other, submit them as
|
|
separate pull requests.
|
|
- Write
|
|
[descriptive commit messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
|
|
|
|
Draft pull requests are also welcome to get feedback early on, or if there is
|
|
something blocking you.
|
|
|
|
## Resources
|
|
|
|
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
|
|
- [Using Pull Requests](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
|
|
- [GitHub Help](https://docs.github.com/en)
|