mirror
/
vapor-docs
mirror of https://github.com/vapor/docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix link as it's not automatic in MKDocs

This commit is contained in:
Tim Condon 2022-07-17 01:40:31 +01:00 committed by GitHub
parent 5552471b63
commit 40fc43b778
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/contributing/contributing.md
View File

@ -6,7 +6,7 @@ Any contribution you make is useful! Even small things like fixing typos make a
## Code of Conduct
Vapor has adopted Swift's Code of Conduct which can be found at https://www.swift.org/code-of-conduct/. All contributors are expected to follow the code of conduct.
Vapor has adopted Swift's Code of Conduct which can be found at [https://www.swift.org/code-of-conduct/](https://www.swift.org/code-of-conduct/). All contributors are expected to follow the code of conduct.
## What to work on
@ -54,4 +54,4 @@ When submitting a pull request there are number of things you should check:
* New tests added for any new behavior or bugs fixed
* New public APIs are documented. We use DocC for our API documentation.
Vapor uses automation to reduce the amount of work needed for many tasks. For pull requests, we use the [Vapor Bot](https://github.com/VaporBot) to generate releases when a pull request is merged. The pull request body and title are used to generate the release notes, so make sure that they make sense and cover what you'd expect to see in release notes. We have more details on [Vapor's contributing guidelines](https://github.com/vapor/vapor/blob/main/.github/contributing.md#release-title).
Vapor uses automation to reduce the amount of work needed for many tasks. For pull requests, we use the [Vapor Bot](https://github.com/VaporBot) to generate releases when a pull request is merged. The pull request body and title are used to generate the release notes, so make sure that they make sense and cover what you'd expect to see in release notes. We have more details on [Vapor's contributing guidelines](https://github.com/vapor/vapor/blob/main/.github/contributing.md#release-title).