@@ -14,32 +14,32 @@ your bug report._
1414When submitting a bug report, please include enough information to reproduce the
1515bug. A good bug report includes the following sections:
1616
17- * ** Description**
17+ - ** Description**
1818
19- Provide a short and clear description of the bug.
19+ Provide a short and clear description of the bug.
2020
21- * ** Steps to reproduce**
21+ - ** Steps to reproduce**
2222
23- Provide steps to reproduce the behavior you are experiencing. Please try to
24- keep this as short as possible. If able, create a reproducible script outside
25- of any framework you are using. This will help us to quickly debug the issue.
23+ Provide steps to reproduce the behavior you are experiencing. Please try to
24+ keep this as short as possible. If able, create a reproducible script outside
25+ of any framework you are using. This will help us to quickly debug the issue.
2626
27- * ** Expected behavior**
27+ - ** Expected behavior**
2828
29- Provide a short and clear description of what you expect to happen.
29+ Provide a short and clear description of what you expect to happen.
3030
31- * ** Screenshots or output**
31+ - ** Screenshots or output**
3232
33- If applicable, add screenshots or program output to help explain your problem.
33+ If applicable, add screenshots or program output to help explain your problem.
3434
35- * ** Environment details**
35+ - ** Environment details**
3636
37- Provide details about the system where you're using this package, such as PHP
38- version and operating system.
37+ Provide details about the system where you're using this package, such as PHP
38+ version and operating system.
3939
40- * ** Additional context**
40+ - ** Additional context**
4141
42- Provide any additional context that may help us debug the problem.
42+ Provide any additional context that may help us debug the problem.
4343
4444## Fixing Bugs
4545
@@ -60,20 +60,20 @@ your hard work, but some features don't fit with the goals of the project.
6060
6161When you do begin working on your feature, here are some guidelines to consider:
6262
63- * Your pull request description should clearly detail the changes you have made.
63+ - Your pull request description should clearly detail the changes you have made.
6464 We will use this description to update the CHANGELOG. If there is no
6565 description, or it does not adequately describe your feature, we may ask you
6666 to update the description.
67- * ` phoneburner/api-handler ` follows a superset of ** [ PSR-12 coding standard] [ psr-12 ] ** , and all pull requests must
67+ - ` phoneburner/api-handler ` follows a superset of ** [ PSR-12 coding standard] [ psr-12 ] ** , and all pull requests must
6868 comply with the coding standard
6969 Please ensure your code does, too. _ Hint: run ` make phpcs ` to check._
70- * Please ** write tests** for any new features you add.
71- * Please ** ensure that tests pass** before submitting your pull request.
70+ - Please ** write tests** for any new features you add.
71+ - Please ** ensure that tests pass** before submitting your pull request.
7272 ` phoneburner/api-handler ` automatically runs tests for pull requests. However,
7373 running the tests locally will help save time. _ Hint: run ` make phpunit ` ._
74- * ** Use topic/feature branches.** Please do not ask to pull from your main branch.
75- * For more information, see "[ Understanding the GitHub flow] [ gh-flow ] ."
76- * ** Submit one feature per pull request.** If you have multiple features you
74+ - ** Use topic/feature branches.** Please do not ask to pull from your main branch.
75+ - For more information, see "[ Understanding the GitHub flow] [ gh-flow ] ."
76+ - ** Submit one feature per pull request.** If you have multiple features you
7777 wish to submit, please break them into separate pull requests.
7878
7979## Developing
@@ -86,7 +86,7 @@ is used externally from the host environment to run most of the common scripts.
8686
8787After cloning this repository locally, execute the following commands:
8888
89- ``` bash
89+ ``` bash
9090cd /path/to/repository
9191make
9292```
@@ -103,7 +103,7 @@ This project uses [PHPStan](https://github.com/phpstan/phpstan) to provide stati
103103code. You may run static analysis manually across the whole codebase with the
104104following command:
105105
106- ``` bash
106+ ``` bash
107107# Static analysis
108108make phpstan
109109```
@@ -114,7 +114,7 @@ This project follows a superset of [PSR-12](https://www.php-fig.org/psr/psr-12/)
114114coding standards, enforced by [ PHP_CodeSniffer] ( https://github.com/squizlabs/PHP_CodeSniffer ) .
115115Rector is also used to enforce code quality and standards
116116
117- ``` bash
117+ ``` bash
118118# Run the code standards linter
119119make phpcs
120120
@@ -139,11 +139,7 @@ make phpunit
139139```
140140
141141[ github ] : https://github.com/PhoneBurnerOpenSource/api-handler
142-
143142[ issues ] : https://github.com/PhoneBurnerOpenSource/api-handler/issues
144-
145143[ pull requests ] : https://github.com/PhoneBurnerOpenSource/api-handler/pulls
146-
147144[ psr-12 ] : https://www.php-fig.org/psr/psr-12/
148-
149145[ gh-flow ] : https://guides.github.com/introduction/flow/
0 commit comments