Option for a trunk-only deployment

[johnbillion]

Is your enhancement related to a problem? Please describe.

I'd like to be assured that a deployment to wordpress.org is as expected before tagging it.

Describe the solution you'd like

If it was possible to perform a trunk-only release via this action, I could then verify the changes in the trunk branch are expected before triggering a regular release which creates the tag.

It would be neat if this action supported a configuration environment variable that instructed it to only deploy the changes to trunk, without also copying them to the tag. It would need to be possible to perform a subsequent release to the tag without it being skipped due to no changed files, so maybe two vars are needed such as NO_TRUNK and ONLY_TRUNK.

[jeffpaul]

An interesting idea, though admittedly not likely something I would look to spend much time on building out, so if that's something you would want to contribute then I would at least look to help with code review, merge, and future support/maintenance.

[danieliser]

I think another option here would be adding an additional output changed-files, that works with both dry-run enabled or disabled. This could then be piped into any other action.

Like @johnbillion I want validation I'm not pushing a broken build some times.

Current workaround is to on creation of draft release we build a zip and attach it to the release, but also run deploy action on dry-run. I'd love to not have to manually check it in the action logs, but its just one more safety net.