-
Notifications
You must be signed in to change notification settings - Fork 800
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
Remove composer dependency listing for built branches #14900
Conversation
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: April 7, 2020. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! I left a few comments below.
Right now, we're left with modified files once the script is done running. It may be good to add something like git checkout -- composer.json
after cd $DIR
in the cleaning up step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to work well in my tests. Merging. Thanks again for the contribution!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think you could rebase this PR to include some of the latest changes we've made to our end to end tests? Right now the end to end tests fail for this PR, so we can't merge it as is.
Thank you!
@jeherve Could you just use the update button? Would much more handy 🙂 |
True, I've rebased now. @brbrr Could you take another look at that test? Thank you! |
#15031 should disable E2E tests for forks. Rebase should fix the issue |
Simplifying by using composer regexp capability
Fixes #13497
Changes proposed in this Pull Request:
Ref: Incompatibility with a WP Composer installation #13497
See my comments inline for detail, and please let me know if there is a better way!
Testing instructions:
N/A
Proposed changelog entry for your changes:
🚀