diff options
Diffstat (limited to 'vendor/spomky-labs/otphp/.github')
| -rw-r--r-- | vendor/spomky-labs/otphp/.github/CONTRIBUTING.md | 25 | ||||
| -rw-r--r-- | vendor/spomky-labs/otphp/.github/ISSUE_TEMPLATE.md | 16 | ||||
| -rw-r--r-- | vendor/spomky-labs/otphp/.github/PULL_REQUEST_TEMPLATE.md | 21 | ||||
| -rw-r--r-- | vendor/spomky-labs/otphp/.github/stale.yml | 17 |
4 files changed, 79 insertions, 0 deletions
diff --git a/vendor/spomky-labs/otphp/.github/CONTRIBUTING.md b/vendor/spomky-labs/otphp/.github/CONTRIBUTING.md new file mode 100644 index 000000000..871735ad1 --- /dev/null +++ b/vendor/spomky-labs/otphp/.github/CONTRIBUTING.md @@ -0,0 +1,25 @@ +# Contributing + +First of all, **thank you** for contributing. + +Bugs or feature requests can be posted online on the GitHub issues section of the project. + +Few rules to ease code reviews and merges: + +- You MUST follow the [PSR-1](http://www.php-fig.org/psr/psr-1/), [PSR-2](http://www.php-fig.org/psr/psr-2/) and [PSR-4](http://www.php-fig.org/psr/psr-4/) coding standards. +- You MUST run the test suite. +- You MUST write (or update) unit tests when bugs are fixed or features are added. +- You SHOULD write documentation. + +We use [Git-Flow](http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/) to automate our git branching workflow. + +To contribute use [Pull Requests](https://help.github.com/articles/using-pull-requests), please, write commit messages that make sense, and rebase your branch before submitting your PR. + +May be asked to squash your commits too. This is used to "clean" your Pull Request before merging it, avoiding commits such as fix tests, fix 2, fix 3, etc. + +Run test suite +------------ + +* install composer: `curl -s http://getcomposer.org/installer | php` +* install dependencies: `php composer.phar install` +* run tests: `vendor/bin/phpunit` diff --git a/vendor/spomky-labs/otphp/.github/ISSUE_TEMPLATE.md b/vendor/spomky-labs/otphp/.github/ISSUE_TEMPLATE.md new file mode 100644 index 000000000..2ceb8da6a --- /dev/null +++ b/vendor/spomky-labs/otphp/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,16 @@ +| Q | A +| -------------------- | ----- +| Bug report? | yes/no +| Feature request? | yes/no +| BC Break report? | yes/no +| RFC? / Specification | yes/no +| Library version | x.y(.z) + +<!-- +Fill in this template according to your issue. +Otherwise, replace this comment by the description of your issue. + +Please consider the following requirements +* You MUST never send security issues here. If you think that your issue is a security one then contact Spomky in private at https://gitter.im/Spomky/ +* You should not post many lines of source code or console logs. Small inputs (approx 5 lines) are acceptable otherwize you should use a third party service (e.g. Pastebin, Chop...). +--> diff --git a/vendor/spomky-labs/otphp/.github/PULL_REQUEST_TEMPLATE.md b/vendor/spomky-labs/otphp/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 000000000..acd0be9fc --- /dev/null +++ b/vendor/spomky-labs/otphp/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,21 @@ +| Q | A +| ------------- | --- +| Branch? | master +| Bug fix? | yes/no +| New feature? | yes/no +| BC breaks? | yes/no +| Deprecations? | yes/no +| Tests pass? | yes/no +| Fixed tickets | #... <!-- #-prefixed issue number(s), if any --> +| License | MIT +| Tests added | <!--highly recommended for new features--> +| Doc PR | <!--highly recommended for new features--> + +<!-- +Fill in this template according to the PR you're about to submit. +Replace this comment by a description of what your PR is solving. + +Please consider the following requirement: +* Modification of existing tests should be avoided unless deemed necessary. +* You MUST never open a PR related to a security issue. Contact Spomky in private at https://gitter.im/Spomky/ +--> diff --git a/vendor/spomky-labs/otphp/.github/stale.yml b/vendor/spomky-labs/otphp/.github/stale.yml new file mode 100644 index 000000000..dc90e5a1c --- /dev/null +++ b/vendor/spomky-labs/otphp/.github/stale.yml @@ -0,0 +1,17 @@ +# Number of days of inactivity before an issue becomes stale +daysUntilStale: 60 +# Number of days of inactivity before a stale issue is closed +daysUntilClose: 7 +# Issues with these labels will never be considered stale +exemptLabels: + - pinned + - security +# Label to use when marking an issue as stale +staleLabel: wontfix +# Comment to post when marking an issue as stale. Set to `false` to disable +markComment: > + This issue has been automatically marked as stale because it has not had + recent activity. It will be closed if no further activity occurs. Thank you + for your contributions. +# Comment to post when closing a stale issue. Set to `false` to disable +closeComment: false |