Suggestion - support pushing to specified branch

[stevoland]

Hi, my company disallows anything pushing to a protected branch without a review.

I'd like to contribute an optional input to specify a branch name if you're happy in principle?

Thanks!

[Justintime50]

Nice! Yeah I think that's a worthwhile feature addition.

Will your workflow be use Homebrew Releaser manually on a separate branch to create the formula file, get it reviewed then merged back to main/master? I can see some potential issues with this use-case since Homebrew Releaser will always use the latest release of a project - it means the Homebrew release would lag behind whatever is actually out there. Curious how this would be used.

[stevoland]

Cool, the plan is:

• Feature branch of the project is merged to trunk branch
• Workflow creates release and calls homebrew releaser with this explicit version
• Homebrew releaser pushes to release-projectX-vY branch of tap
• Workflow creates tap PR
• Workflow does actually auto-approve and merge this (it's a long story)

Am currently achieving this on 2.0.3 by using skip_commit and a push after but that's no longer doable with the /tmp folder stuff.

Thanks!

[Justintime50]

Right on, seems feasible. Yeah happy to accept a PR if you'd like to put something up, following the conventions of the project to accomplish that 🙂

Yeah, that /tmp garbage is super unfortunate, spent hours on that refactor and couldn't get it working any other way. I apologize if it messed up your workflow - didn't expect anyone to be seeing into the internals of the process.