Skip to content
This repository was archived by the owner on Dec 27, 2022. It is now read-only.

Fix migration notice on new WP install #124

Merged
merged 2 commits into from
Feb 27, 2017
Merged

Fix migration notice on new WP install #124

merged 2 commits into from
Feb 27, 2017

Conversation

PatelUtkarsh
Copy link
Member

@PatelUtkarsh PatelUtkarsh commented Feb 27, 2017

Fixes #123

@PatelUtkarsh PatelUtkarsh changed the title Fixes #123: Fix migration notice on new WP install Fix migration notice on new WP install Feb 27, 2017
@PatelUtkarsh PatelUtkarsh changed the title Fix migration notice on new WP install [WIP] Fix migration notice on new WP install Feb 27, 2017
@coveralls
Copy link

Coverage Status

Coverage decreased (-2.1%) to 74.661% when pulling 40f153a on fix/123 into bdfb0ec on develop.

@coveralls
Copy link

coveralls commented Feb 27, 2017

Coverage Status

Coverage increased (+0.05%) to 76.824% when pulling 71a4ae0 on fix/123 into bdfb0ec on develop.

@PatelUtkarsh PatelUtkarsh changed the title [WIP] Fix migration notice on new WP install Fix migration notice on new WP install Feb 27, 2017
$migrate_obj->expects( $this->once() )
->method( 'changeset_migrate' )
->with( 1, true )
->will( $this->returnValue( false ) );
Copy link
Contributor

@westonruter westonruter Feb 27, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fancy PHPUnit usage. 👍

@westonruter westonruter added this to the 0.6.0 milestone Feb 27, 2017
@westonruter westonruter merged commit bf0f7f7 into develop Feb 27, 2017
@westonruter westonruter deleted the fix/123 branch February 27, 2017 17:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants