Skip to content

HttpError: Resource not accessible by integration #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ZyLyao opened this issue Jan 10, 2023 · 8 comments
Open

HttpError: Resource not accessible by integration #30

ZyLyao opened this issue Jan 10, 2023 · 8 comments

Comments

@ZyLyao
Copy link

ZyLyao commented Jan 10, 2023

Run joshcai/[email protected]
[Tue, 10 Jan 2023 01:31:51 GMT] Getting submission from LeetCode, offset 0
[Tue, 10 Jan 2023 01:31:51 GMT] Default branch for ZyLyao/My-Leetcode-Practice: main
[Tue, 10 Jan 2023 01:31:51 GMT] Syncing 3 submissions...
[Tue, 10 Jan 2023 01:31:51 GMT] Committing solution for add_two_integers...
[Tue, 10 Jan 2023 01:31:51 GMT] HttpError: Resource not accessible by integration
at /home/runner/work/_actions/joshcai/leetcode-sync/v1.5/node_modules/@octokit/rest/node_modules/@octokit/request/dist-node/index.js:88:21
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async commit (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/src/action.js:69:24)
at async Object.sync (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/src/action.js:240:34)
at async main (/home/runner/work/_actions/joshcai/leetcode-sync/v1.5/index.js:31:3)
Error: HttpError: Resource not accessible by integration

@GrayBurford
Copy link

Hello Joshcai,

I receive the same error as ZyLyao above when trying to sync for the first time (looking to sync my previously completed Leetcode problems with GitHub).

image

@ZyLyao
Copy link
Author

ZyLyao commented Jan 15, 2023

Hi, GrayBurford

I had a few successful runs after setting up private token of my GitHub account. The action is not finally setup as I do not understand what the actual issue is. Perhaps you can try setting the token and see if that works for you.

Zeyi

@GrayBurford
Copy link

Hi ZyLyao,

Are you referring to GitHub's Personal Access Token? Thank you for your reply!

Gray

@ZyLyao
Copy link
Author

ZyLyao commented Jan 16, 2023 via email

@GrayBurford
Copy link

ZyLyao,

Thank you, will try it out.

Gray

@PabloCuestaMorer
Copy link

Yes. If you hardcode a classic token in the workflow. It works. Until a fix comes out, it's the only option that has worked for me. If anyone finds a better one, let me know.

Pablo.

@saumya-tiwari
Copy link

image you can check this as well. Mine was set as Readonly. @ZyLyao

@ZyLyao
Copy link
Author

ZyLyao commented Jun 26, 2023

image you can check this as well. Mine was set as Readonly. @ZyLyao

I will try this. Thanks for the reply, @saumya-tiwari.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants