Yoann Celton 623db82a57 Initial Commit

Fixed typos

Update README.md

Ninja 5.6 test

Update README.md

Update CONTRIBUTING.md

Update CONTRIBUTING.md

update skeleton project

Switched to composer require

Remove version from composer require

Composer detects the latest stable version (only 0.x should specify the version)
http://blog.doh.ms/2014/10/13/installing-composer-packages/

Update README.md

Fix duplicate require-dev entry

Update LICENSE to use Markdown

Update LICENSE.md link

Add .gitattributes file

Fix documentation

Fix typo

Remove extra newline

Added php_analyzer: true to scritunizer

Rename scrutinizer.yml to .scrutinizer.yml

updated scrutinizer reference

consistent headlines in CHANGELOG.md

This fits also more into the style from http://keepachangelog.com/

Harmonize package variables

fix syntax in CHANGELOG.md

Readme: use relative paths to CONTRIBUTING.md and contributors

new year

update copyright year

remove duplicate field

the `:author_website` option was listed twice

Add a security section

Add Ocular as dev-dependency, fixes HHVM issues too apparently

Updated package name to be able to submit to Packagist

Reverting

Typo in README.md

Update SkeletonClass.php

Added php 7.0 and allow it to fail

Added php 7.0 and allow it to fail

Removed PHP 5.3

Removed --dev flag

According to Travis-Ci, "You are using the deprecated option "dev". Dev packages are installed by default now."

travis: PHP 7.0 nightly added

simplifies configuration

This removes a few settings that had no effect anymore.

Update CONTRIBUTING.md

Not everyone may be familiar with the term (or the details of) "squashing." A link to the git documentation would be helpful in this case.

Added editor configuration

Add use of Composer scripts like 'composer test'

Update `composer test` to simply use `phpunit`

Encourage developers to read the change log

docs(testing): Update testing to use composer test

https://getcomposer.org/doc/articles/scripts.md#writing-custom-commands

Added end_of_line & some more info about this file

> It is acceptable and often preferred to leave certain EditorConfig properties unspecified. For example [...] if a property is not standardized in your project (end_of_line for example), it may be best to leave it blank.

http://editorconfig.org/#file-format-details

I added ``end_of_line`` nonetheless, as I think there is an agreement to always use ``lf``.

[Travis] Test lowest version dependencies

Use Packagist Release badge instead of GH release

Because most repos don't do releases, they just tag their revisons. Which suffices for Composer/Packagist - but the current badge would simply state "Release: None"...

Alternatively the GH Tag badge could be used instead.

Do not call ocular in PHP 7.0 and HHVM

We cannot be dead certain that those support code coverage, so they would break the Scrutinizer build the following message "Scrutinizer was notified that the tests failed." even though all builds succeeded.

At the moment HHVM seems to work, excluding it nonetheless.
Also now it correlates with three runs configured in 13bd2abaeb/.scrutinizer.yml (L23)

use composer test

Moved all links to the bottom of README.md

Forgot to update image alt text

Switch to local phpunit

This ensures consistency across platforms and testing by using the same version of PHPUnit, rather than whatever is globally installed by the system.

Revert `composer test` in composer.json

First, composer will push its bin to the top of the $PATH when running composer scripts, so this isn't strictly necessary. Secondly, using `/` will fail on Windows. This reverts one of the changes previously made in 54f6cbc606.

Add sudo false to Travis config

Add comment about sudo false Travis config

Added CONDUCT.md

Many people are great developers, but awful awful human beings. This will remind their robot brains how to human with other humans in a way that doesn't make one of those humans sad or really angry.

Mention CONDUCT.md in the README

Added disclaimer to code of conduct application

Update CONDUCT.md

use `:vendor` placeholder

to make the package more useful for general use, replace references to
`thephpleague` and `league` with `:vendor`.

Added PSR2 check

Bump minimum PHP version to 5.4

Disallow PHP 7 failures

PHP 7 is now stable and Travis is using these stable builds for testing

Use "Keep a CHANGELOG" principles

See http://keepachangelog.com/

Add "type" to composer.json

travis: drop PHP 5.4

composer: bump to PHP 5.5, allow PHP 7 in safe way

Resolved issue#67

Removed blank lines

Update copyright year

Add .styleci.yml

Removed redundant Test namespace

Allow PHPUnit v5

Prefer dist + cache for Travis builds

To speed up builds

added composer script for psr2 formatting

Enhancement: Keep packages sorted

Update php version required

In order to require only supported php version,
update minimum php version required from 5.5 to 5.6.

travis: bump min version to PHP 5.6, add PHP 7.1

Min version is PHP 5.6, see composer: ad403d7a63/composer.json (L20)
Also PHP 7.1 is available on Travis

Create PULL_REQUEST_TEMPLATE.md

Create ISSUE_TEMPLATE.md

Use PHP-specific examples in Issue template

Updated CoC to CC 1.4

Added coc contact email address

Added script prefill.php to replace all :variables

Added script prefill.php to replace all :variables

Use PHP-specific examples

Add PHP Codesniffer as development dependency

Add Composer scripts "check-codestyle" & "fix-codestyle"

Adjust Contribution guide

Ignore errors and warnings in PHPCS

Refs: https://github.com/thephpleague/skeleton/pull/41#issuecomment-104071697

Thanks to @gsherwood

Fix indentation

Replace check-codestyle & fix-codestyle with check-style & fix-style respecively

set the author email as the contact in the CONDUCT file

add the xml.dist extesion to the prefil script

Use phar version of ocular

It's impossible to install the latest version of Guzzle due
ocular (used to upload code coverage) depending on guzzlehttp/guzzle ~3.0.

See https://github.com/scrutinizer-ci/ocular/blob/master/composer.json

Closes #95

Inspired by https://github.com/Ocramius/ProxyManager/blob/master/.travis.coverage.sh

Add .travis.coverage.sh to gitattributes

Don't use separate file for uploading code coverage

Remove .travis.codecoverage.sh from git attributes

Remove useless items from PR checklist

These rules will be checked in the Travis build.

Add note about CI

Fix #87 | "docs" entry in .gitignore?

Remove docs directory out of .gitignore and locate it in .gitaatributes

Fix typo

Add missing word

Adding in recommended directory structure

Update README.md

Update year in LICENSE.md

Fix tests directory name

Because almost all League projects uses `tests/`, including this skeleton.

Update README.md

Remove Composer self-updating from .travis.yml

It is done automatically by Travis.

Revert "Remove Composer self-updating from .travis.yml"

Revert "Revert "Remove Composer self-updating from .travis.yml""

Fix minor grammar error in code of conduct

Replace placeholders in tests as well

trailing comma not allowed

put array back the way it was

Update composer.json

Just to accept the latest PHPUnit version

Fix tests on PHP 5.6 & HHVM

Rename CONDUCT.md to CODE_OF_CONDUCT.md

GitHub looks for [CODE_OF_CONDUCT.md](https://help.github.com/articles/adding-a-code-of-conduct-to-your-project/)

fix capitalization

test on 7.2

7.2 is released now, so let's test it.

Spelling mistake?

not my strong area but I think this should be `practices` not `practises`

change the year in LICENSE.md

Remove TAP adapter

Added a phpcs.xml.dist file

Add phpcs to gitignore and gitattributes file

Use new PHP analysis engine

Update travis to test on PHP7.3

init 1

2022-06-23 21:20:13 +10:00

3.1 KiB

Raw Blame History

Contributor Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

Using welcoming and inclusive language
Being respectful of differing viewpoints and experiences
Gracefully accepting constructive criticism
Focusing on what is best for the community
Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

The use of sexualized language or imagery and unwelcome sexual attention or advances
Trolling, insulting/derogatory comments, and personal or political attacks
Public or private harassment
Publishing others' private information, such as a physical or electronic address, without explicit permission
Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at :author_email. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4

3.1 KiB Raw Blame History