Skip to content
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

remote: Repository not found #243

Open
razb-viola opened this issue Jul 8, 2024 · 2 comments · May be fixed by #248
Open

remote: Repository not found #243

razb-viola opened this issue Jul 8, 2024 · 2 comments · May be fixed by #248

Comments

@razb-viola
Copy link

I get this error:

remote: Repository not found.
  Error: fatal: repository 'https://github.com/REPO/' not found
  The process '/usr/bin/git' failed with exit code 128
  Waiting 14 seconds before trying again

And this is the workflow yaml:

- uses: actions/checkout@v4
- uses: dorny/paths-filter@v3
        id: filter
        with:
          filters: |
            auth:
              - 'backend/auth/src/**'

and the step of dorny gets the error mentioned above - without reaching to the step of running the service later in the yaml, that's why I didn't provide it here.

I tried both checkout@v4 and v3.
I gave permissions of pull request read, as follow:

permissions:
      pull-requests: read
@1um
Copy link

1um commented Jul 9, 2024

It seems the permissions field overrides already granted permissions; here is the fix:

permissions:
      contents: read
      pull-requests: read

@alexanderjophus
Copy link

alexanderjophus commented Aug 1, 2024

Thanks for this GHA, it's amazing. I'm still getting the issue when I try your fix above. I assume what you're saying is if we don't have the permissions field at all then it just inherits whatever is in the over arching github repo settings?

nvm, I'm an idiot and hit a slightly different problem, solved here: #212 (comment)

@134130 134130 linked a pull request Aug 30, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

3 participants