Skip to content
This repository was archived by the owner on Jan 29, 2020. It is now read-only.

Commit 3a6e0ea

Browse files
committed
Merge branch 'hotfix/24'
Close #24
2 parents 128e88b + 101fc37 commit 3a6e0ea

File tree

6 files changed

+45
-30
lines changed

6 files changed

+45
-30
lines changed

.gitattributes

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
/docs export-ignore
2-
/test export-ignore
31
/.coveralls.yml export-ignore
42
/.gitattributes export-ignore
53
/.gitignore export-ignore
64
/.travis.yml export-ignore
75
/composer.lock export-ignore
6+
/docs/ export-ignore
87
/mkdocs.yml export-ignore
98
/phpcs.xml export-ignore
109
/phpunit.xml.dist export-ignore
10+
/test/ export-ignore

.gitignore

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
docs/html/
2-
vendor/
3-
zf-mkdoc-theme/
4-
clover.xml
5-
coveralls-upload.json
6-
phpunit.xml
7-
zf-mkdoc-theme.tgz
1+
/clover.xml
2+
/coveralls-upload.json
3+
/docs/html/
4+
/phpunit.xml
5+
/vendor/
6+
/zf-mkdoc-theme.tgz
7+
/zf-mkdoc-theme/

LICENSE.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
Copyright (c) 2017, Zend Technologies USA, Inc.
2-
32
All rights reserved.
43

54
Redistribution and use in source and binary forms, with or without modification,

composer.json

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,14 +15,6 @@
1515
"zendframework",
1616
"zend-expressive"
1717
],
18-
"config": {
19-
"sort-packages": true
20-
},
21-
"extra": {
22-
"zf": {
23-
"config-provider": "Zend\\Expressive\\Hal\\ConfigProvider"
24-
}
25-
},
2618
"support": {
2719
"docs": "https://docs.zendframework.com/zend-expressive-hal/",
2820
"issues": "https://github.com/zendframework/zend-expressive-hal/issues",
@@ -65,6 +57,14 @@
6557
"ZendTest\\Expressive\\Hal\\": "test/"
6658
}
6759
},
60+
"config": {
61+
"sort-packages": true
62+
},
63+
"extra": {
64+
"zf": {
65+
"config-provider": "Zend\\Expressive\\Hal\\ConfigProvider"
66+
}
67+
},
6868
"scripts": {
6969
"check": [
7070
"@cs-check",

docs/ISSUE_TEMPLATE.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,19 @@
1+
- [ ] I was not able to find an [open](https://github.com/zendframework/zend-expressive-hal/issues?q=is%3Aopen) or [closed](https://github.com/zendframework/zend-expressive-hal/issues?q=is%3Aclosed) issue matching what I'm seeing.
2+
- [ ] This is not a question. (Questions should be asked on [slack](https://zendframework.slack.com/) ([Signup for Slack here](https://zendframework-slack.herokuapp.com/)) or our [forums](https://discourse.zendframework.com/).)
3+
14
Provide a narrative description of what you are trying to accomplish.
25

36
### Code to reproduce the issue
47

8+
<!-- Please provide the minimum code necessary to recreate the issue -->
9+
510
```php
611
```
712

813
### Expected results
914

15+
<!-- What do you think should have happened? -->
16+
1017
### Actual results
1118

19+
<!-- What did you actually observe? -->

docs/PULL_REQUEST_TEMPLATE.md

Lines changed: 20 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,25 @@
11
Provide a narrative description of what you are trying to accomplish:
22

3-
- Are you fixing a bug?
4-
- Detail how the bug is invoked currently.
5-
- Detail the original, incorrect behavior.
6-
- Detail the new, expected behavior.
3+
- [ ] Are you fixing a bug?
4+
- [ ] Detail how the bug is invoked currently.
5+
- [ ] Detail the original, incorrect behavior.
6+
- [ ] Detail the new, expected behavior.
7+
- [ ] Base your feature on the `master` branch, and submit against that branch.
8+
- [ ] Add a regression test that demonstrates the bug, and proves the fix.
9+
- [ ] Add a `CHANGELOG.md` entry for the fix.
710

8-
- Are you creating a new feature?
9-
- Why is the new feature needed? What purpose does it serve?
10-
- How will users use the new feature?
11+
- [ ] Are you creating a new feature?
12+
- [ ] Why is the new feature needed? What purpose does it serve?
13+
- [ ] How will users use the new feature?
14+
- [ ] Base your feature on the `develop` branch, and submit against that branch.
15+
- [ ] Add only one feature per pull request; split multiple features over multiple pull requests
16+
- [ ] Add tests for the new feature.
17+
- [ ] Add documentation for the new feature.
18+
- [ ] Add a `CHANGELOG.md` entry for the new feature.
1119

12-
- Is this related to quality assurance?
13-
- Detail why the changes are necessary.
20+
- [ ] Is this related to quality assurance?
21+
<!-- Detail why the changes are necessary -->
1422

15-
- Is this related to documentation?
16-
- Is it a typographical and/or grammatical fix?
17-
- Is it new documentation?
23+
- [ ] Is this related to documentation?
24+
<!-- Is it a typographical and/or grammatical fix? -->
25+
<!-- Is it new documentation? -->

0 commit comments

Comments
 (0)