From de64d4543e64d2ba847ff65562bec6c8af30dcd2 Mon Sep 17 00:00:00 2001 From: Radu Marias Date: Fri, 13 Dec 2024 05:32:45 +0200 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c01d18e6..c2cdcb0c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -7,15 +7,18 @@ Unless you explicitly state otherwise, any Contribution intentionally submitted defined in the Apache License shall be dual-licensed as above, without any additional terms or conditions. 1. Join [slack](https://bit.ly/3UU1oXi) and join `#dev-beginners` channel -2. Become familiar with docs and code by reading the [ramp-up](docs/readme/Ramp-up.md) guide -3. **Ask the owner of the repository to add your GitHub username to the repository** so that you can work on issues and +2. **Ask the owner of the repository to add your GitHub username to the repository** so that you can work on issues and be able to create your own branches and not need to fork the repo + +# Devs & QA automation (which steps apply) + +3. Become familiar with docs and code by reading the [ramp-up](docs/readme/Ramp-up.md) guide 4. Pick an open issue or a task in the corresponding [project](https://github.com/users/radumarias/projects/1) for the - repo that you'll be working on. You can + repo you'll work on. You can see [good for first issues](https://github.com/radumarias/rencfs/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) that you can pick from -5. **Assign the issues you are working on to you and move them to the corresponding status column as you are progressing - on them. If the task is not an issue yet, convert it to issue first** +5. **Assign the issues you are working on to you and move them to the corresponding status column as you progress + . If the task is not an issue yet, convert it to an issue first** 6. Make the changes in your branch 7. Add docs as they apply 8. Add tests, benchmarks, and examples for your changes, if applicable @@ -38,3 +41,7 @@ defined in the Apache License shall be dual-licensed as above, without any addit 16. Respond to any comments 17. **DON'T MERGE THE PR YOURSELF. LEAVE THAT TO REPOSITORY OWNERS** 18. In the end, ideally, it will be merged into `main` + +# QA manual + +Please follow these [steps](docs/readme/Testing.md).