Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random post #9

Merged
merged 9 commits into from
Dec 15, 2019
Merged

Random post #9

merged 9 commits into from
Dec 15, 2019

Conversation

pretzlaw
Copy link

No description provided.

rmp-up added 9 commits December 15, 2019 00:35
The current implementation of FixtureCommand is a bit quick and dirty.
From time to time we try to decouple as much logic as possible from this.
This time a function parameter has been swapped to a class param
so that we can delegate/swap the loops in the __invoke method some time.
The upcoming feature covers generation of completely random posts.
This does not fit to the current section which only explains the fields.
So we create a sub-section for fields to have siblings for other things.
Lesser test may make CI faster
* No need for wp-cli/entity-command
* Marked supported PHP Version
* Marked lowest possible WP Version (if johnpbloch/wordpress is used)
* Swapped roave/security-advisories to testing where it belongs
* Changes to testing / dropped obsolete things
We use coveralls.io to measure the code coverage over time.
With some release the executable has been renamed so it
didn't uploads coverage.xml anymore in the end.
To prevent this and other possible issues
we install coverals alone and run the executable for '^2.2'.

* .gitignore: Also ignore the coverage file in root dir
@pretzlaw pretzlaw added this to the 0.7 milestone Dec 15, 2019
@pretzlaw pretzlaw merged commit 455d9bb into release/0.7 Dec 15, 2019
@pretzlaw pretzlaw deleted the feature/random-post branch December 15, 2019 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant