markdownlint-rule-relative-.../CONTRIBUTING.md

# 💡 Contributing

Thanks a lot for your interest in contributing to **markdownlint-rule-relative-links**! 🎉

## Code of Conduct

**markdownlint-rule-relative-links** adopted the [Contributor Covenant](https://www.contributor-covenant.org/) as its Code of Conduct, and we expect project participants to adhere to it. Please read [the full text](./CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.

## Open Development

All work on **markdownlint-rule-relative-links** happens directly on this repository. Both core team members and external contributors send pull requests which go through the same review process.

## Types of contributions

- Reporting a bug.
- Suggest a new feature idea.
- Correct spelling errors, improvements or additions to documentation files (README, CONTRIBUTING...).
- Improve structure/format/performance/refactor/tests of the code.

## Pull Requests

- **Please first discuss** the change you wish to make via [issue](https://github.com/theoludwig/markdownlint-rule-relative-links/issues) before making a change. It might avoid a waste of your time.

- Ensure your code respect linting.

- Make sure your **code passes the tests**.

If you're adding new features to **markdownlint-rule-relative-links**, please include tests.

## Commits

The commit message guidelines adheres to [Conventional Commits](https://www.conventionalcommits.org/) and [Semantic Versioning](https://semver.org/) for releases.
chore: initial commit 2023-01-02 15:23:16 +01:00			`# 💡 Contributing`

			`Thanks a lot for your interest in contributing to markdownlint-rule-relative-links! 🎉`

build(deps): update latest 2023-05-13 16:03:06 +02:00			`## Code of Conduct`

			`markdownlint-rule-relative-links adopted the [Contributor Covenant](https://www.contributor-covenant.org/) as its Code of Conduct, and we expect project participants to adhere to it. Please read [the full text](./CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.`

			`## Open Development`

			`All work on markdownlint-rule-relative-links happens directly on this repository. Both core team members and external contributors send pull requests which go through the same review process.`

chore: initial commit 2023-01-02 15:23:16 +01:00			`## Types of contributions`

			`- Reporting a bug.`
			`- Suggest a new feature idea.`
			`- Correct spelling errors, improvements or additions to documentation files (README, CONTRIBUTING...).`
			`- Improve structure/format/performance/refactor/tests of the code.`

			`## Pull Requests`

fix: update author - Théo LUDWIG 2023-06-24 10:11:32 +02:00			`- Please first discuss the change you wish to make via [issue](https://github.com/theoludwig/markdownlint-rule-relative-links/issues) before making a change. It might avoid a waste of your time.`
chore: initial commit 2023-01-02 15:23:16 +01:00
			`- Ensure your code respect linting.`

			`- Make sure your code passes the tests.`

			`If you're adding new features to markdownlint-rule-relative-links, please include tests.`

			`## Commits`

build(deps): update latest 2023-05-13 16:03:06 +02:00			`The commit message guidelines adheres to [Conventional Commits](https://www.conventionalcommits.org/) and [Semantic Versioning](https://semver.org/) for releases.`