You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* release/1.0.0: (71 commits)
version bumped to 1.0.0
Updated CHANGELOG [ci skip]
[Bug] NormalizeArrayListener should not run on FormRequest
[Travis] Changed dist from precise to trusty.
[Test] Use mocked HTTP client in testGetAccessTokenFail
[CHANGELOG] Imported 0.8.4 version from support [ci skip]
[CHANGELOG] Imported missing versions from support [ci skip]
Update docblock for Client::setApiVersion
[docs] Request shields.io badges over SSL [ci skip]
BranchRestrictions.php wurden online mit Bitbucket bearbeitet
[README] Updated link to license file
[README] migrate from .org to .io
[docs] updated permalink for refs/branches & refs/tags
[docs] updated permalink for refs/branches & refs/tags
updated changelog
[docs] updated min req. PHP version
Removed Credits section from Readme
Added Security section in Readme
Added CONTRIBUTING.md & update Contribute section from Readme
Updated scripts section from composer.json
...
First of all, thank you for taking time to contribute!
4
+
5
+
Contributions are accepted via Pull Requests on [Bitbucket][repo]. Sometimes, our free time is very limited and could take a while until we review your pull request, so please be patient while you wait for code review.
6
+
7
+
We don't mind getting questions, so if you have any, please open a new issue on our [tracker][repo].
8
+
9
+
## Pull Requests
10
+
11
+
Here are a few rules which you should follow, in order to ease code review and merging:
12
+
13
+
1.**Follow [PSR-2 Coding Standard][PSR-2]**
14
+
-**Create feature branches** - We don't pull from your (master|develop) branch!
15
+
-**One pull request per feature** - If you need/want to change more than one thing, please send multiple pull requests.
16
+
-**Consider our release cycle** - We follow [SemVer v2.0.0][semver]. Breaking public APIs is not acceptable.
17
+
-**(Add|Update) tests when applicable.**
18
+
-**Document any change in behaviour** - Update documentation and/or readme file when applicable.
19
+
20
+
Sometimes you might be asked to also [squash your commits][squash] (*we don't want commits such as `fix 1`, `fix <n>`, `now its working`, etc*). This is done in order to keep a clean and coherent VCS history.
0 commit comments