HttpError: Resource not accessible by integration

[ZyLyao]

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]

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).

[ZyLyao]

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]

Hi ZyLyao,

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

Gray

[ZyLyao]

Yes. FYI, I used the classic token option.

GrayB @.***>于2023年1月16日 周一上午11:47写道：

Hi ZyLyao,

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

Gray

— Reply to this email directly, view it on GitHub https://github.com/joshcai/leetcode-sync/issues/30#issuecomment-1384483540, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPZLZVVMIVH3KMRGGHMV4TWSWQW3ANCNFSM6AAAAAATWCPVOI . You are receiving this because you authored the thread.Message ID: @.***>

[GrayBurford]

ZyLyao,

Thank you, will try it out.

Gray

[PabloCuestaMorer]

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]

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

[ZyLyao]

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

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