| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@szepeviktor What do you think of this? Does it solve your needs? |
Sorry, something went wrong.
Sorry, something went wrong.
|
@swissspidy The repository was created: https://github.com/wp-cli/wp-cli-shim |
Sorry, something went wrong.
|
@schlessera Thanks! Can you add me to the repo so I can add an initial composer.json file? |
Sorry, something went wrong.
|
@schlessera OK so I pushed a branch intending to create a PR but because it was the first branch that became the default 🤦 https://github.com/wp-cli/wp-cli-shim Can you make main the default, remove add-v0 and make any other changes as you see fit? |
Sorry, something went wrong.
|
@schlessera OK, so now I suppose what's left is making sure that the ACTIONS_BOT token has access to the new repo, then it should just work. Once it does, we can tag what's currently in the repo with v2.9.0, afterwards there will be nightly updates people can use with dev-main. Not sure if we need branch-alias there as well, that would probably complicate things. |
Sorry, something went wrong.
|
@schlessera wanna give this a try for next release? |
Sorry, something went wrong.
|
Hi @swissspidy, I came here from #134. I'm aware of @johnpbloch's great https://github.com/johnpbloch/wp-cli-phar package, and we use it in our organization, but having a first-party repository would be even better (especially in times of supply chain attacks becoming worryingly regular). Therefore, please allow me to ask if there are any plans to move this PR forward. |
Sorry, something went wrong.
|
Thanks for the ping! Work on this kinda stalled in favor of wp-cli/wp-cli#5920, where we wanted to take a step back and identify the actual problem we're trying to solve. If you'd like to leave a comment expressing your interest & what you would like to see solved, that would be very helpful. |
Sorry, something went wrong.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 30086f0e-935f-4d0e-9797-1a0e8b674bf7 You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file. Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
The `deploy-shim` job downloaded an artifact named `wp`, but the build job uploads it as `wp-cli-phar` containing `wp-cli.phar`, so the download failed and the subsequent `chmod`/`git add` had no file to operate on. Download the correct artifact and rename the Phar to `wp`, which is what `wp-cli/wp-cli-shim` declares as its `bin`. Also align the job with the existing `deploy` job: * Give it a distinct display name, as both were labelled "Deployment". * Pin `actions/checkout`, `actions/download-artifact` and `ad-m/github-push-action` to the same SHAs used elsewhere in this workflow, instead of floating tags and `@master`. * Push to `main` explicitly. Without it the action defaults to the current ref, which would push to a branch named after the bundle's ref rather than the shim's default branch. * Push tags, so the "Tag stable release" step is no longer a no-op. * Skip on `workflow_dispatch`, matching `deploy`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RHtjyXkZh8X16sBgmidSQi
| Back | FazBrowse Home | New Git URL |
Assumes the existence of a new wp-cli/phar repository with a composer.json such as this one:
{ "name": "wp-cli/wp-cli-shim", "description": "Composer-based WP-CLI Phar", "license": ["MIT"], "require": { "php": ">=5.6" }, "conflict": { "wp-cli/wp-cli" : "*" }, "bin": ["wp-cli.phar"] }And I think that's all that's needed.
To-do:
Fixes #134
Fixes wp-cli/ideas#145