Private github registries no longer supported?

[jramke]

Hey,

are private github registries no longer supported? I tried setting it up using a fine grained personal access token with read permission for content on my repo. Then tried to register it using the tokens command and also using the auth --token command. Also used --no-cache.

Always this output:

There was an error fetching `jsrepo-manifest.json` from github/jramke/jsrepo-test.

This may be for one of the following reasons:
1. Either `jsrepo-manifest.json` or the containing repository doesn't exist
2. Your repository path is incorrect (wrong branch, wrong tag)
3. You are using an expired access token or a token that doesn't have access to this repository
4. The cached state for this git provider is incorrect (try using --no-cache)

When i set the repo to public everything works as expected.

When i send a test request with the Authorization header token from https://ungh.cc/#tag/default/get/repos/{owner}/{repo} i also get a 404.

Am i missing something?

[ieedan]

Hmm I wonder if ungh doesn't support airhead requests. Will have to take a look later. Strange that you'd be the first to notice this 🤔

[ieedan]

Yeah ig they don't support private repos. Which makes sense since that's not their claim really.

When I have the chance I should revert #541 and we should just use the fetch API to the GitHub API.

[jramke]

That would be great 🙏

[ieedan]

Fixed in #593 sorry this took so long!

[jramke]

No problem, thanks for the fix :)