gitadmin/freeCodeCamp
1
0
Fork 0
mirror of https://github.com/freeCodeCamp/freeCodeCamp.git synced 2026-05-28 18:26:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update reply template (#51234)

Browse Source
This commit is contained in:
Mrugesh Mohapatra
2023-08-12 23:20:19 +05:30
committed by GitHub
parent ff19789791
commit 30ad1d72b9
1 changed files with 13 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reply-templates.md
+13 -21
View File
@@ -131,40 +131,32 @@ If you think we're wrong in closing this issue, please request for it to be reop
## Adding Comment About Newbie Mistakes
```markdown
Hi there,
Hello,
Thanks for creating this pull request.
Firstly, thank you for submitting this pull request!
Please ensure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously. Respect the requirements to earn the respect of your fellow maintainers. You will also save everyone time :)
As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.
Since you are new here, please slow down and read our [contributing guidelines](https://contribute.freecodecamp.org), as we see that you may still need to catch up on a few things.
If you're unfamiliar with certain aspects, our [contributing guidelines](https://contribute.freecodecamp.org) are a helpful resource to get you up to speed.
<details>
<summary>Here are some examples (expand)</summary>
1. Do not edit files directly on GitHub – while you can, it's not a good idea.
<summary>**Friendly Pointers (click to expand)**</summary>
Typos and formatting errors can break the tests.
1. **Editing on GitHub:** While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.
2. Use the correct way to link issues.
2. **Linking Issues:** Please ensure you link issues using the designated method. Simply update the `XXXXXX` in the PR description to include the issue number. This keeps our records organized and clear.
Add the issue number only in the description of the PR by updating the `XXXXXX`. Do not just add issue numbers everywhere and anywhere you feel like.
3. **Engaging with the Team:** We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.
4. Keep mentions and review requests to a minimum.
We understand you are excited about contributing, and our maintainers will get back to you when they can.
5. Do not work directly off your `main` branch.
You can always create a new branch for the changes you are working on. That way, you can sync change to your PR branch as the main repository moves ahead while your PR is waiting in the merge queue.
4. **Branch Management:** It's a good practice not to work directly off your `main` branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.
</details>
Don't worry. You don't have to close this PR. Feel free to ask specific queries on improving your PR here; someone will guide you.
Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.
We are happy you are excited to contribute and appreciate you taking the time to help us. Looking forward to more contributions!
Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!
Happy Contributing.
**Happy Contributing!** 🌟
```
## Issue Not Triaged
@@ -243,4 +235,4 @@ We typically do not assign issues. Instead, we accept the first pull request tha
Issues labelled with `help wanted` or `first timers only` are open for contributions.
Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you.
```
```