SbloodyS commented on code in PR #17114:
URL: 
https://github.com/apache/dolphinscheduler/pull/17114#discussion_r2030444579


##########
docs/docs/en/contribute/join/contribute.md:
##########
@@ -38,3 +38,5 @@ If you want to implement a Feature or fix a Bug. Please refer 
to the following:
 * When you're done, send a Pull Request to dolphinscheduler, please refer to 
the《[Submit Guide-Submit Pull Request Process](./submit-code.md)》
 
 If you want to submit a Pull Request to complete a Feature or fix a Bug, it is 
recommended that you start with the `good first issue`, `easy-to-fix` issues, 
complete a small function to submit, do not change too many files at a time, 
changing too many files will also put a lot of pressure on Reviewers, it is 
recommended to submit them through multiple Pull Requests, not all at once.
+
+_Contributed as part of GSoC 2025 application by Marya Alamzeb_

Review Comment:
   ```suggestion
   ```



##########
docs/docs/en/contribute/join/contribute.md:
##########
@@ -38,3 +38,5 @@ If you want to implement a Feature or fix a Bug. Please refer 
to the following:
 * When you're done, send a Pull Request to dolphinscheduler, please refer to 
the《[Submit Guide-Submit Pull Request Process](./submit-code.md)》
 
 If you want to submit a Pull Request to complete a Feature or fix a Bug, it is 
recommended that you start with the `good first issue`, `easy-to-fix` issues, 
complete a small function to submit, do not change too many files at a time, 
changing too many files will also put a lot of pressure on Reviewers, it is 
recommended to submit them through multiple Pull Requests, not all at once.
+
+_Contributed as part of GSoC 2025 application by Marya Alamzeb_

Review Comment:
    Please remove unnessnary change.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to