covid19/cwa-documentation
covid19
/
cwa-documentation
mirror of https://github.com/corona-warn-app/cwa-documentation
1
0
Fork 0
Code Releases Activity

Fixed typos in CONTRIBUTING.md

This commit is contained in:
Johann Weiher 2020-05-13 10:25:42 +02:00 committed by GitHub
parent 648fa885f2
commit a4422a6d3a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
CONTRIBUTING.md
View File

@ -12,23 +12,23 @@ We appreciate your courtesy of avoiding political questions here. Issues which a
We use GitHub to manage reviews of pull requests.
* If you are a new contributor, see: [Steps to Contribute](#steps-to-contribute)
* If you are a new contributor, see: [Steps to contribute](#steps-to-contribute)
* If you have a trivial fix or improvement, go ahead and create a pull request, addressing (with `@...`) a suitable maintainer of this repository (see [CODEOWNERS](CODEOWNERS) of the repository you want to contribute to) in the description of the pull request.
* If you have a trivial fix or improvement, go ahead and create a pull request, addressing (with `@...`) a suitable maintainer of this repository (see [CODEOWNERS](CODEOWNERS) of the repository you want to contribute to) in the description of the pull request.
* If you plan to do something more involved, please reach out to us and send an [email](mailto:corona-warn-app.opensource@sap.com). This will avoid unnecessary work and surely give you and us a good deal of inspiration.
* Relevant coding style guidelines are available in the respective sub-repositories as they are programming language-dependent.
* Relevant coding style guidelines are available in the respective sub-repositories as they are programming language dependent.
## Steps to Contribute
## Steps to contribute
Should you wish to work on an issue, please claim it first by commenting on the GitHub issue that you want to work on. This is to prevent duplicated efforts from other contributors on the same issue.
If you have questions about one of the issues, please comment on them, and one of the maintainers will clarify.
We kindly ask you to follow the [Pull Request Checklist](#Pull-Request-Checklist) to ensure reviews can happen accordingly.
We kindly ask you to follow the [Pull request checklist](#Pull-Request-Checklist) to ensure reviews can happen accordingly.
## Contributing Code
## Contributing code
You are welcome to contribute code in order to fix a bug or to implement a new feature.
@ -36,7 +36,7 @@ The following rule governs code contributions:
* Contributions must be licensed under the [Apache 2.0 License](LICENSE)
## Contributing Documentation
## Contributing documentation
You are welcome to contribute documentation to the project.
@ -44,9 +44,9 @@ The following rule governs documentation contributions:
* Contributions must be licensed under the same license as code, the [Apache 2.0 License](LICENSE)
## Pull Request Checklist
## Pull request checklist
* Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you may be asked to rebase your changes.
* Branch from the master branch and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master, you may be asked to rebase your changes.
* Commits should be as small as possible while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).