Would it be possible to add the base_ref as an output if triggered from the pull_request context?

[grahame-student]

Details

My team are looking at ways of identifying where testing can be streamlined and one idea is to compare certain build outputs with those generated by the branch they want to merge into.

Having easy access to the base_ref of a PR would simplify matters.

[GrantBirki]

👋 Hey @grahame-student! This Action is heavily inspired by the github/branch-deploy Action and even takes a lot of code from that project as well.

In the github/branch-deploy project, there is actually a base_ref output. I'll go ahead and make this project match by adding one to this project as well.

Note: This output will likely only be available as a "best effort" attempt. What I mean by this is that base_ref will only really be available if the github/command workflow is running in the context of a pull request. This value would likely not be available if you are running github/command in the context of an issue.

[grahame-student]

That's awesome, thanks. I understand the limitations, they make perfect sense.

I've been exploring the IssueOps concept as an enabler for my team, so for most things we're highly likely to be in the context of a pull_request and not an issue.

I've been using some actions/github-script magic to get the base_ref so far, but having it exposed by github/command will be much tidier.

[GrantBirki]

Done! 🎉 This has been released in v1.5.0.