|
1 |
| -**This pull request makes the following changes:** |
2 |
| -* Fixes collabo-community/put-repo-name-where-the-issue-is-located-here#putTheIssueNumberHere |
| 1 | +#### This pull request makes the following changes |
3 | 2 |
|
4 |
| -**General checklist** |
5 |
| -- [ ] File or folder now contains changes as specified in the issue i worked on |
6 |
| -- [ ] I have linked the issue I worked on to this pull request submitted by me |
| 3 | +> [!IMPORTANT] |
| 4 | +> Remove this alert notice and supply this crucial information to help reviewers understand your submission better. If the issue ticket is on GitHub, follow the direction below to link your issue ticket to this pull request. If the issue ticket is not on GitHub, Replace the part after the word "Fixes" with the ticket link. |
7 | 5 |
|
8 |
| -**Testing checklist** |
| 6 | +* Fixes collabo-community/put-repo-name-where-the-GitHub-issue-is-located-here#putTheGitHubIssueNumberHere |
9 | 7 |
|
10 |
| -Replace this text with the testing checklist from the issue this pull request fixes. |
| 8 | +# |
11 | 9 |
|
| 10 | +#### General checklist |
| 11 | + |
| 12 | +> [!IMPORTANT] |
| 13 | +> Remove this alert notice and follow the direction below to ensure and confirm that your pull request follows community guidelines. Tick the checkboxes accordingly. |
| 14 | +
|
| 15 | +- [ ] My pull request adheres to the [Collabo Community pull request guidelines](https://docs.collabocommunity.com/pull-request-guidelines). |
| 16 | +- [ ] I have read and understood the **Pull request guideline extension** section found at the bottom of this pull request description/body. |
| 17 | +- [ ] I have replaced the dummy text under the subheading **Testing checklist** below with the testing checklist from the issue ticket I'm working on. |
| 18 | + |
| 19 | +# |
| 20 | + |
| 21 | +#### Testing checklist |
| 22 | + |
| 23 | +Replace this dummy text with the testing checklist from the issue this pull request fixes (use checkboxes similar to how it's done in the **General checklist** above). |
| 24 | + |
| 25 | +# |
| 26 | + |
| 27 | +#### How to run project |
| 28 | + |
| 29 | +> [!IMPORTANT] |
| 30 | +> Did something change in this PR about how to run the project locally? If so, remove this alert notice (along with the tip) and follow the direction below. |
| 31 | +
|
| 32 | +> [!TIP] |
| 33 | +> If this PR did not change how the project is run locally, you can just remove this how to run project section totally. |
| 34 | +
|
| 35 | +Replace this dummy text with new information on how to run the project (preferably using a list e.g. unordered list or ordered list). |
| 36 | + |
| 37 | +# |
| 38 | + |
| 39 | +#### Pull request guideline extension |
| 40 | + |
| 41 | +> [!NOTE] |
| 42 | +> Do not remove this note or section. This talks about extra things to take note of, in addition to the directions given in the Collabo Community pull request guidelines. |
| 43 | +
|
| 44 | +We appreciate the time taken to help tackle issue tickets within the Collabo Community. Please go ahead to submit your pull request even if it is not yet completed, and push to the pull request actively. This will allow us to know that you have not abandoned the issue ticket. However, you should only alert reviewers about your pull request as explained below, to avoid flooding their GitHub notifications unnecessarily. |
| 45 | + |
| 46 | +"Ready for review" implies that things are working as expected, according to how it is specified in the issue ticket you are working on. Ensure that you test the code that you are working on, that it works as expected. Don't just request for review when your pull request is not yet done and working. |
| 47 | + |
| 48 | +The only time you should be making people review something incomplete is: if you want to show them what's not working, so that they can send help or guidance. If this is the case, be explicit about this in our Discord community or in the comment of your pull request (after you have submitted the pull request). |
0 commit comments