Support Github merge queue from pull-request configuration

[LecrisUT]

Description

This is a follow-up to #2266. Although that provides a way to configure the CI for merge queue, this requires quite a lot of duplication of each test configuration. Playing around with the merge queue, I've found that it always require a status check to be defined and passed for PRs.

But this would be the exact same name match and be taken from the pull request trigger configuration. So ideally we should not require the user to setup a different configuration, but instead reuse the one from the pull request trigger, with the same name format.

There are a few caveats such as how to fill the PR-only environment variables or what context to use, for which I suggest to treat it the same as a commit trigger and require the user to account for that difference.

Benefit

No response

Importance

No response

What is the impacted category (job)?

Testing Farm tests, Copr builds

Workaround

• There is an existing workaround that can be used until this feature is implemented.

Participation

• I am willing to submit a pull request for this issue. (Packit team is happy to help!)

[lbarcziova]

Hi @LecrisUT and thanks for the proposal. I agree this could improve the UX a lot. Is this somehow blocking you right now? (probably the linked tmt issue).

There are a few caveats such as how to fill the PR-only environment variables or what context to use, for which I suggest to treat it the same as a commit trigger and require the user to account for that difference.

Yes, I believe there would be few things to figure out. @mfocko you were looking into this previously, do you have any cautions/suggestions about the implementation?

[LecrisUT]

Is this somehow blocking you right now? (probably the linked tmt issue).

Yes indeed we are, since it otherwise requires duplicating our whole testing jobs.