We'll have to fix this upstream in https://github.com/wp-cli/scaffold-package-command, which is the command used to automatically generate the readmes for all our commands.

https://github.com/wp-cli/scaffold-package-command/blob/b923d846aacd216554303b4583cc65eef3dd0cc5/templates/readme-installing.mustache#L12

The branch name is actually passed as an argument there:

https://github.com/wp-cli/scaffold-package-command/blob/b923d846aacd216554303b4583cc65eef3dd0cc5/src/ScaffoldPackageCommand.php#L251

So it should be possible to pass the branch name to the Mustache template.

If I'd just merge this PR, then the change would get reverted with the next automated readme update. That's why it must get addressed in the scaffold-package-command.

Is this something you'd be able to help address?

Understood! I'm not sure when I'll get to creating a more involved PR off that branch (either just renaming or else passing in a variable to the template).

I'll close this PR though.

@brianhogg I gotcha covered! wp-cli/scaffold-package-command#241