Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

pantheon-systems / wp-redis Public

Notifications You must be signed in to change notification settings
Fork 68
Star 227

Code
Issues 22
Pull requests 5
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Fix `wp redis cli` by using `proc_open()` directly#268

Merged

danielbachhuber merged 3 commits intomasterpantheon-systems/wp-redis:masterfrom use-proc-open-directlypantheon-systems/wp-redis:use-proc-open-directlyCopy head branch name to clipboard

Feb 24, 2020

+14-6

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 24, 2020

Use proc_open() equivalent directly, instead of WP_CLI::launch()
danielbachhuber
committed
Cast as an int just to be clear
danielbachhuber
committed
Update README for v0.8.3
danielbachhuber
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.