I can almost guarantee that credential you found is someone’s personal
access token anyways. I don’t think anything has been set up org wide
besides the GitHub app for webhooks and checkouts.

On Thu, Oct 29, 2020 at 02:10 Istvan Toth <st...@apache.org> wrote:

> There was quite a bit of traffic on this list about having a credential
> that is able to comment on GitHub PRs, but we (Phoenix project) still have
> this problem.
>
> What I am trying to do is posting a comment on the PR like this:
> https://github.com/apache/phoenix/pull/940#issuecomment-716666308
>
> (Development versions of Yetus are supposed to be able to add the same
> information to the *Checks* tab, but that's not what I'm after this time)
>
> I have tried these credentials:
> asf-ci
> 9fa62308-3a11-4abe-a22a-b6bb63d07362
> b0c25240-9660-4100-b67d-b3bdb2609cd6
> 683f5dcf-5552-4b28-9fb1-6a6b77cf53dd
>
> but Yetus is not able to comment on the PR with these, additionally I get
> the following message in the Jenkins log:
>
> Could not update commit status, please check if your scan credentials
> belong to a member of the organization or a collaborator of the repository
> and repo:status scope is selected
>
> I have added a personal access to my GitHub account, that has *repo:status
> *
> and* public_repo* permissions (only), to the Jenknis credentials, and the
> job works as expected and can comment to GitHub.
>
> I would like to have a way to add comments that do not reply on my personal
> account. I can see that the HBase project uses a separate github account
> credential *apache-hbase-at-github.com <http://apache-hbase-at-github.com
> >*
>  for this purpose. That solution would be fine for us too, but I could not
> find a way to grant permissions to any account to our repos.
>
> I'd like to have either a credential in Jenkins that is able to comment to
> repos, or help with granting permission to a github robot account to the
> repos, so that I can use that instead of mine for the job.
>
> best regards
> Istvan
>

Reply via email to