mirror of
https://github.com/2006-Scape/Parabot.git
synced 2026-07-07 00:38:16 +00:00
[TASK] Moved description down
This commit is contained in:
@@ -17,9 +17,6 @@ What types of changes does your code introduce? Check all the boxes that apply:
|
|||||||
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
|
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
|
||||||
- [ ] Cleanup (non-breaking change which cleans up the code)
|
- [ ] Cleanup (non-breaking change which cleans up the code)
|
||||||
|
|
||||||
### Description
|
|
||||||
...
|
|
||||||
|
|
||||||
### Final checklist
|
### Final checklist
|
||||||
Go over all the following points and check all the boxes that apply.
|
Go over all the following points and check all the boxes that apply.
|
||||||
If you're unsure about any of these, don't hesitate to ask. We're here to help!
|
If you're unsure about any of these, don't hesitate to ask. We're here to help!
|
||||||
@@ -34,4 +31,7 @@ Your pull request will be tested via Travis CI to automatically indicate that yo
|
|||||||
|
|
||||||
If it reports back that there are problems, you go to [the Travis system](https://travis-ci.org/Parabot/Parabot) and check the log report for your pull request to see what the problem was.
|
If it reports back that there are problems, you go to [the Travis system](https://travis-ci.org/Parabot/Parabot) and check the log report for your pull request to see what the problem was.
|
||||||
If you add new code to fix a Travis building issue/problem, then take note that you need to check the next pull request in the Travis system.
|
If you add new code to fix a Travis building issue/problem, then take note that you need to check the next pull request in the Travis system.
|
||||||
Travis issue numbers are different from GitHub issue numbers.
|
Travis issue numbers are different from GitHub issue numbers.
|
||||||
|
|
||||||
|
### Description
|
||||||
|
...
|
||||||
Reference in New Issue
Block a user