<commit_before># VLibrary

VLibrary is a minimal jumpstart for small BDD library development with PHPSpec
and Phing.

# Get started immediately

To begin a fresh project with vlibrary, create your new git repository as usual,
then follow these instructions within your repository's root to get started.

1. `git remote add -f vlibrary git://github.com/Moult/vlibrary.git`
2. `git merge -Xtheirs vlibrary/master`
3. Get [Composer](http://getcomposer.org) `curl -s
   http://getcomposer.org/installer | php` and then run `php composer.phar
   install --dev`. This is needed to set up testing tools (installs into
   `bin/`).
4. Use [Phing](http://www.phing.info/) to run `phing all` in project root. This
   will run `phpspec`, `phpcs`, `pdepend`, `phpmd`, `phpcpd`, `phpdcd`
   and `phpdoc2`. `phing` by itself is a shorthand to run just PHPSpec. For more
   information, see `phing -projecthelp`
5. Start developing. Specs are in `spec/`, documentation is in `docs/`. Any
   build logs generated by `phing all-log` useful for CI can be found in
   `build/`.

Remember to replace README.md and LICENSE with your own!
<commit_msg>Bump readme<commit_after># vlibrary

vlibrary is a minimal jumpstart for small BDD library development with PHPSpec
and Phing.

# Get started immediately

To begin a fresh project with vlibrary, create your new git repository as usual,
then follow these instructions within your repository's root to get started.

1. `git remote add -f vlibrary git://github.com/Moult/vlibrary.git`
2. `git merge -Xtheirs vlibrary/master`
3. Get [Composer](http://getcomposer.org) `curl -s
   http://getcomposer.org/installer | php` and then run `php composer.phar
   install --dev`. This is needed to set up testing tools (installs into
   `bin/`).
4. Use [Phing](http://www.phing.info/) to run `phing all` in project root. This
   will run `phpspec`, `phpcs`, `pdepend`, `phpmd`, `phpcpd`, `phpdcd`
   and `phpdoc2`. `phing` by itself is a shorthand to run just PHPSpec. For more
   information, see `phing -projecthelp`
5. Start developing. Specs are in `spec/`, documentation is in `docs/`. Any
   build logs generated by `phing all-log` useful for CI can be found in
   `build/`.

Remember to replace README.md and LICENSE with your own!

{'fraction_non_alphanumeric': 0.10292812777284827, 'fraction_numerical': 0.005323868677905945, 'mean_word_length': 3.8599137931034484, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5148723', 'n_tokens_mistral': 708, 'n_tokens_neox': 701, 'n_words': 307}