You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting the following when running eb --check-github with a personal access token that really has the proper gists permission:
Checking status of GitHub integration...
Making sure we're online...OK
* GitHub user...bedroge => OK
* GitHub token...ghp..MW0 (len: 40) => OK (validated)
* git command...OK ("git version 2.31.1; ")
* GitPython module...OK (GitPython version 3.1.18)
The authenticity of host 'github.com (140.82.121.3)' can't be established.
ECDSA key fingerprint is SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
* push access to bedroge/easybuild-easyconfigs repo @ GitHub...OK
* creating gists...FAIL (gist_url: https://gist.github.com/bedroge/6e0503bc018f7de1a7d63f3e994b0c71)
* location to Git working dirs... OK (/home1/p251204/easybuild)
One or more checks FAILed, GitHub configuration not fully complete!
See http://easybuild.readthedocs.org/en/latest/Integration_with_GitHub.html#configuration for help.
Status of GitHub integration:
* --from-pr: OK
* --new-pr: OK
* --review-pr: OK
* --update-pr: OK
* --upload-test-report: not supported
@branfosj just confirmed he's seeing the same issue. Interestingly, things seem to work fine anyway (it uploaded this test report right after running the above command: easybuilders/easybuild-easyconfigs#17610 (comment)), so it looks like there's something wrong with this check.
The text was updated successfully, but these errors were encountered:
I'm getting the following when running
eb --check-github
with a personal access token that really has the propergists
permission:@branfosj just confirmed he's seeing the same issue. Interestingly, things seem to work fine anyway (it uploaded this test report right after running the above command: easybuilders/easybuild-easyconfigs#17610 (comment)), so it looks like there's something wrong with this check.
The text was updated successfully, but these errors were encountered: