leetcode-sync icon indicating copy to clipboard operation
leetcode-sync copied to clipboard

Problem with running workflow file

Open somixyz opened this issue 3 years ago • 1 comments

I have followed all these steps as described in the README file, but I keep getting this error.

build Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/runner/work/_actions/somixyz/leetcode_solutions/v1.0'. Did you forget to run actions/checkout before running your local action?

What should I do here ?

somixyz avatar Sep 07 '22 20:09 somixyz

Hi @somixyz, I don't have permission to see the link - do you mind sharing the configuration you added, e.g. whatever is under .github/workflows?

joshcai avatar Sep 11 '22 17:09 joshcai

Hi, I have the same error, did you resolve it @somixyz? @joshcai under .github/workflows, I only have sync_lc.yml with the same content as in your instructions. PFA Screenshot 2023-01-08 171729 Screenshot 2023-01-08 171801

AbhinavJaintle avatar Jan 08 '23 11:01 AbhinavJaintle

Hmm I see a similar issue reported in https://github.com/actions/checkout/issues/692, do you know if yours also fails the same way on the second run?

joshcai avatar Jan 09 '23 07:01 joshcai

This is my experience, for developers and anyone who encounters any problem with this in the future:

  • The first mistake I made was not correctly linking the uses value to joshcai/[email protected] which resulted in the error Can't find 'action.yml', 'action.yaml' or 'Dockerfile'.
  • Once I linked the uses value properly, I found a new error (which is still unresolved) Error: Request failed with status code 401.
  • Then I just went to try out the chrome extension.
  • Even within the chrome extension, it still produces an error -- where you can't successfully link an already present repo and have to make a new one, but once a new one is made, it works fine.

Notes:

  • The chrome extension may give HttpError: API rate limit exceeded for installation ID error but that's only because you've exceeded github's daily limit of commits (don't worry, it'll sync from the same submission a day later).
  • I have not yet tried to perform the same workflow(without extension) with version @v1.4 instead of @v1.5 but I suspect that the problem may be due to the new version.

Hope this helps!

AbhinavJaintle avatar Jan 11 '23 10:01 AbhinavJaintle