Update: allow "force" parameter in plugin.disable() #2843
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
till force-pushed the plugin-disable-force branch from ceeb980 to 7cccee1 Compare Signed-off-by: till <till@php.net>
till force-pushed the plugin-disable-force branch from 7cccee1 to d005711 Compare Contributor Author
| Not sure about the last failure, looks like something else. The other tests (which I previously broke), complete now. |
milas approved these changes Jul 29, 2022
Contributor Author
| Thanks @milas |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
FYI, I used the docker/cli for inspiration:
https://github.com/docker/cli/blob/86e1f04b5f115fb0b4bbd51e0e4a68233072d24b/vendor/github.com/docker/docker/client/plugin_disable.go#L11-L19