Add pull_request trigger to release workflow

[gliptak]

https://github.com/gliptak/winboat/actions/runs/17529895526?pr=1

[gliptak]

@TibixDev please approve workflow run

[fat0troll]

Approved the workflow run.

[fat0troll]

It would be nice if the pull request build end up somewhere in artifacts so the author of the pull request could use them to test the changes in the provided build by themselves before asking for a merge.

UPD: found it, ignore this comment.

[fat0troll]

Ah, oops, I'm blind, found them: https://github.com/TibixDev/winboat/actions/runs/17530023679#artifacts

Could you add a step to the workflow that can post such a link to the pull request itself?

[gliptak]

thank you @fat0troll

could be modeled after https://github.com/open-turo/actions-go/blob/f1747e80b0dccc25f57c632099397a4ff522415d/prerelease/action.yaml#L186-L198

happy to work this as a followup PR

[gliptak]

@fat0troll updated with link posting

gliptak#1 (comment)

[gliptak]

@TibixDev please approve workflow run

[fat0troll]

Approved the workflow run.

[gliptak]

👍 the run failed with a 403 (although it was successful at gliptak#1 (comment)

I added https://github.com/TibixDev/winboat/pull/66/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R4
maybe a repo/org level setting update needed (Settings -> Action -> General -> Workflow Permissions and choose read and write permissions?)

[gliptak]

@TibixDev please approve workflow run

[fat0troll]

Approved the run. Also checked the permissions with @TibixDev, it seems like it should work, it has read and write permissions.

[gliptak]

thank you @fat0troll looks like below?

[TibixDev]

I had to do the checkmark, should be good now?

[gliptak]

thank you @TibixDev please approve workflow run

[gliptak]

Still 403. I’m not clear how configurations differ