Open danielbachhuber opened 6 years ago
I've never done that before. If it could be automated to go out with every release, I'd be up for figuring it out. I recently made this project generate a .phar with every release.
Ah, I think you need to submit a PR with the changed version. Here's WP-CLI's formulae: https://github.com/Homebrew/homebrew-core/blob/master/Formula/wp-cli.rb
Or maybe it's a bot that creates it? https://github.com/tcely/homebrew-core/pull/243
Hm, okay. I am creating PRs from automation tasks via the updatinate project. Seems entirely feasible that I could also create a PR from the Travis before-deploy
task.
Here are the criteria for being added to homebrew. Cgr may or may not qualify. It might be appropriate to put it in some alternate tap.
I guess I could also maintain my own tap at consolidation/homebrew-cgr. Then, I'd only need to push to this git repo when publishing a new version.
Have you considered distributing
cgr
via Homebrew?