feat: Allow for passing custom merge target

[kamilogorek]

See getsentry/craft#355 for more details.

[bruno-garcia]

renders a new field in the publish action to type in? Can it be prefiled with the repo's main branch name?

[kamilogorek]

Yes, it renders the new field if configured in the target repo.

It cannot be prefilled because this repo, nor action-prepare-release has any knowledge about the target repo, those it doesn't know its default branch name. It can be master, it can be main, but we don't know that afaik. Only craft knows that when you run it.

[BYK]

It cannot be prefilled because this repo, nor action-prepare-release has any knowledge about the target repo, those it doesn't know its default branch name.

action-prepare-release knows what repo it runs in with a GITHUB_TOKEN so it should be able to determine the main branch?

[kamilogorek]

I’ll research that. It would be nice, as we could remove default parsing override in publish repo, as the value would be always there.

[BYK]

I think this should be optional until everybody gets to the latest version of action-prepare-release. Otherwise you'll have lots of failures.

[kamilogorek]

True, forgot about the fallback for destructuring. Because other than this, merge_target can be undefined, as it should evaluate to empty env variable, thus being skipped in cli call. (not that I haven't test any of this yet, as its not decided what we'll do with the original issue just yet).

[kamilogorek]

I cannot find any way to use dynamic value for inputs.default in composite gh action :(

I'm also starting to wonder if there is even a point doing this, as craft itself handles default branch 🤔

[BYK]

I'm also starting to wonder if there is even a point doing this, as craft itself handles default branch 🤔

I'd just leave it empty so Craft does "the right thing"™️

[jan-auer]

@kamilogorek would be great if we add a section to the readme on how to publish from/to a non-default branch similar to how we describe "CalVer".