forked from samba-team/samba
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update documentation and fix comments
- Loading branch information
1 parent
3f46b7b
commit 6431939
Showing
21 changed files
with
846 additions
and
471 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,11 @@ | ||
# Сode contribution workflow | ||
|
||
1. Find an open issue or create a new issue on issue tracker for the feature you want to contribute. | ||
2. Fork the project on GitHub. You need to create a feature-branch for your work on your fork, as this way you be able to submit a pull request. | ||
3. Make any necessary changes to the source code. | ||
4. Add tests that verify that your contribution works as expected and modify existing tests if required. | ||
5. Run all tests and make sure all of them pass. | ||
6. Run code coverage to check if the lines of code you added are covered by unit tests. | ||
7. Once your feature is complete, prepare the commit with appropriate message and the issue number. | ||
8. **Create a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) and wait for the users to review. When you submit a pull request, please, agree to the terms of [CLA](CLA.md).** | ||
# Code contribution workflow | ||
|
||
1. Find an open issue or create a new issue on issue tracker for the feature you want to contribute. | ||
2. Fork the project on GitHub. You need to create a feature-branch for your work on your fork, as this way you be able to submit a pull request. | ||
3. Make any necessary changes to the source code. | ||
4. Add tests that verify that your contribution works as expected and modify existing tests if required. | ||
5. Run all tests and make sure all of them pass. | ||
6. Run code coverage to check if the lines of code you added are covered by unit tests. | ||
7. Once your feature is complete, prepare the commit with appropriate message and the issue number. | ||
8. **Create a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) and wait for the users to review. When you submit a pull request, please, agree to the terms of [CLA](CLA.md).** | ||
9. Once everything is done, your pull request gets merged. Your feature will be available with the next release and your name will be added to AUTHORS. |
Oops, something went wrong.