Searched hist:"72 d6673ebbc99f5177af3d60d6b1dde969ef44e8" (Results 1 – 2 of 2) sorted by relevance
| /optee_os/.github/workflows/ |
| H A D | notify.yml | 72d6673ebbc99f5177af3d60d6b1dde969ef44e8 Tue Nov 18 08:57:52 UTC 2025 Jerome Forissier <jerome.forissier@linaro.org> ci: move notify_maintainers to a separate workflow
The default ${{ secrets.GITHUB_TOKEN }} does not allow write access to
pull requests created from a fork, even when the permissions: block is
supposed to allow it (it does for PRs created from the same repository
but not from forks). As a result, the create_issue_comment() returns a
"403: Forbidden" error. See [1] for example.
Fix the issue by moving the notify_maintainers job to a separate
workflow which is triggered on the pull_request_target event. The
mechanism is explained in .github/workflows/notify.yml.
Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Link: https://github.com/OP-TEE/optee_os/actions/runs/19434849286/job/55602878593?pr=7426 [1]
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | ci.yml | 72d6673ebbc99f5177af3d60d6b1dde969ef44e8 Tue Nov 18 08:57:52 UTC 2025 Jerome Forissier <jerome.forissier@linaro.org> ci: move notify_maintainers to a separate workflow
The default ${{ secrets.GITHUB_TOKEN }} does not allow write access to
pull requests created from a fork, even when the permissions: block is
supposed to allow it (it does for PRs created from the same repository
but not from forks). As a result, the create_issue_comment() returns a
"403: Forbidden" error. See [1] for example.
Fix the issue by moving the notify_maintainers job to a separate
workflow which is triggered on the pull_request_target event. The
mechanism is explained in .github/workflows/notify.yml.
Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Link: https://github.com/OP-TEE/optee_os/actions/runs/19434849286/job/55602878593?pr=7426 [1]
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|