From 75439a82f933f74a9804d1e32de7687ad8debcbe Mon Sep 17 00:00:00 2001 From: Radu Marias Date: Sun, 15 Dec 2024 21:14:23 +0200 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8e8e38c0..f08ed5ed 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,8 +38,8 @@ defined in the Apache License shall be dual-licensed as above, without any addit 14. Push your changes, and if there are any errors, fix them before you push them 15. Create a `PR` back to the `parent` repo targeting the `main` branch with the title as the GitHub issue title, including `#ID`. Also, include the link to GitHub issue in the description, saying like `Fix for ` for bugs or `Implementation for ` for features and others 16. Request review from owners of the repository by adding them to the `Reviewers` field -17. ![image](https://github.com/user-attachments/assets/5ac0313d-4175-44d1-8d1e-d18da773ab32) - After you've created the PR, go to the GitHub issue, and in the mid-right of the page, press the gear icon from above, select `radumarias/rencfs`, then write the PR number and select it. This will link the two, and when the PR is merged, it will close the issue too +17. After you've created the PR, go to the GitHub issue, and in the mid-right of the page, press the gear icon from the below image, select `radumarias/rencfs`, then write the PR number and select it. This will link the two, and when the PR is merged, it will close the issue too + ![image](https://github.com/user-attachments/assets/5ac0313d-4175-44d1-8d1e-d18da773ab32) 18. In the project, move the item to `In Code Review` 19. Monitor the checks (GitHub actions runs) and fix the code if they are failing 20. Respond to any comments