When tfaga is triggered by current pull request by issue comment or sth., it can update the test status in that pull request.
But when tfaga is triggered by repository_dispatch, which could come from a pull request in another github repo, it still need to update the test status.
I don't know how tfaga update the pull request status, but before we use tfaga, we use this plugin to create the test status in target pull request. Here is the example:
name: Create test status
uses: octokit/request-action@v2.x
with:
route: 'POST /repos/osbuild/osbuild-composer/statuses/${{ target_pull_request.sha }}'
context: 'RHEL 9.4 test'
state: pending
description: 'RHEL 9.4 - Test has been running...'
target_url: ${{ test_job.html_url }}
Type of issue
None
Description
When tfaga is triggered by current pull request by issue comment or sth., it can update the test status in that pull request. But when tfaga is triggered by repository_dispatch, which could come from a pull request in another github repo, it still need to update the test status.
Here is more details:
I suggest we can add a parameter gith_sha in https://github.com/sclorg/testing-farm-as-github-action?tab=readme-ov-file#miscellaneous, and use github_token to create status in target pull request.
I don't know how tfaga update the pull request status, but before we use tfaga, we use this plugin to create the test status in target pull request. Here is the example:
Reproducer
No response