[
https://issues.apache.org/jira/browse/LOG4J2-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393209#comment-17393209
]
ASF subversion and git services commented on LOG4J2-3085:
---------------------------------------------------------
Commit ae3f19ac66acf711831535f5db36efd449d5f47a in logging-log4j2's branch
refs/heads/release-2.x from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=ae3f19a ]
LOG4J2-3085 Skip certain CI jobs for external PRs.
> Fix GitHub Actions workflows for PRs from forks
> -----------------------------------------------
>
> Key: LOG4J2-3085
> URL: https://issues.apache.org/jira/browse/LOG4J2-3085
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Volkan Yazici
> Priority: Major
>
> When a GitHub Actions workflow is triggered by a PR from an _external_
> repository, certain build steps (_"Publish Test Results"_, _"Upload Test
> Reports"_, etc.) in the workflow fail due to insufficient privileges with
> ["Resource not accessible by
> integration"|https://github.com/actions/first-interaction/issues/10] error.
> This renders the entire CI result useless to determine if a PR is introducing
> a breaking change. This story aims to improve that situation.
> In [the relevant GitHub Actions
> ticket|https://github.com/actions/first-interaction/issues/10], there are a
> couple of alternatives suggested and they seem to be promising as a starting
> point.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
