[
https://issues.apache.org/jira/browse/SPARK-31330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074124#comment-17074124
]
Nicholas Chammas commented on SPARK-31330:
------------------------------------------
Unfortunately, it seems I jumped the gun on sending that dev email about the
GitHub PR labeler action.
It has a fundamental limitation that currently makes it [useless for
us|https://github.com/actions/labeler/tree/d2c408e7ed8498dfdf675c5f8d133ab37b6f8520#pull-request-labeler]:
{quote}Note that only pull requests being opened from the same repository can
be labeled. This action will not currently work for pull requests from forks –
like is common in open source projects – because the token for forked pull
request workflows does not have write permissions.
{quote}
Additional detail:
[https://github.com/actions/labeler/issues/12#issuecomment-525762657]
I'll keep my eye on that Action in case they somehow lift or work around the
limitation on forked repositories.
Of course, we can always implement this functionality ourselves, but the
attraction of the GitHub Action was that we could reuse an existing, tested,
and widely adopted implementation.
> Automatically label PRs based on the paths they touch
> -----------------------------------------------------
>
> Key: SPARK-31330
> URL: https://issues.apache.org/jira/browse/SPARK-31330
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 3.1.0
> Reporter: Nicholas Chammas
> Priority: Minor
>
> We can potentially leverage the added labels to drive testing, review, or
> other project tooling.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
