I tried that as well and that does not work.
I think that the problem is that I am not sure what the permissions on the tokens should be. When I set the permission for my specific repository, it does not “stick”. I mean - I hit “update” but then I see there is no access configured for that repository.
Should I choose specific permissions from the list? There are so many permissions there, and that seems weird.
Yes, there are a lot of settings, I used the fine-grained pat. I used the following fields:
Token name
Expiration
Description
Only select repositories
Select repositories
Repository permissions
Contents (set to Read-only)
Generate token
I set all of these, but apparently, I also had to choose specifically some of the repository permissions. After doing that, I could add my package. Thanks!
Today I ran into a related issue.
My use case is the following:
I have a dockerfile which is using a private repository (a Julia package). Thus I activate and instantiate that package.
The package has dependencies which are other private repositories.
The following worked for me. In package mode you can add a private repository like this:
add "https://ghp_my_personal_git_access_token@github.com/kafisatz/TBManagerProxmox.jl.git"