Add action-pr-link feature

[134130]

Description

• Closes When an action has spawned from a PR, provide a link back to the PR #6206

Test URLs

• https://github.com/refined-github/refined-github/actions

Screenshot

[134130]

When the action is defined as check run, matchingPullRequests is missing and checkSuite > checkRuns contains some values.
Need to find the way of figure out related PR.

I think this is GitHub API's bug. The matchingPullRequests need to be always returns some values when trigger event is pull_request regardless of checkRuns existing.

[yakov116]

I don't understand why can you not the the pr number from the issue title?
update Readme #1

[134130]

@yakov116 That is not the PR number, The WorkflowRun Number

[yakov116]

Aha, use api v3

refined-github/source/features/bypass-checks.tsx

Line 16 in 3eb6977

// Impossible with v4 https://github.com/refined-github/refined-github/pull/6550#discussion_r1176346110

[fregante]

Thank you for the PR!

[134130]

I found the pull_request field works correctly only on administrator of repository regardless v4 or v3.

[fregante]

I found the pull_request field works correctly only on administrator of repository regardless v4 or v3.

As mentioned before, I don’t think this feature should use the API, but just the observer to alter the links adding ?pr= wherever possible. We can see how well this works and potentially add the API in a month if it brings substantial benefits.

[134130]

Yes I'm working with not using api call :)
Just note for future.

[fregante]

This is great!

One limitation I found is that GitHub does not support issues, not via pr= nor via issue=

For example this workflow runs on both, but only the PRs can be linkified: https://github.com/refined-github/refined-github/actions/workflows/labeler.yml

[134130]

One limitation I found is that GitHub does not support issues, not via pr= nor via issue=

For example this workflow runs on both, but only the PRs can be linkified: refined-github/refined-github/actions/workflows/labeler.yml

😢 But It is awesome that we can implement this feature without calling API.
Even if with calling API, I could not find the way to get the issue which triggered the workflow.