Add build step for wp-cli/wp-cli-shim

[swissspidy]

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:

• Add hashes and/or signature for verification
• Maybe rename to wp-cli/wp-cli-shim or something

Fixes#134
Fixeswp-cli/ideas#145

[danielbachhuber]

@szepeviktor What do you think of this? Does it solve your needs?

[szepeviktor]

Everything from Pascal gets the Seal of Approval from me.

[schlessera]

@swissspidy The repository was created: https://github.com/wp-cli/wp-cli-shim

[swissspidy]

@schlessera Thanks! Can you add me to the repo so I can add an initial composer.json file?

[schlessera]

@swissspidy Done.

[swissspidy]

@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?

[swissspidy]

@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.

[swissspidy]

@schlessera wanna give this a try for next release?

[swissspidy]

Suggested change

branch: gh-pages