Replies: 2 comments
-
What made the difference here isn't that you created a fine-grained token -- the previous token was also fine-grained, as other tokens are not supported. More likely the old token had simply expired. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Noted, thanks.
…-------- Original Message --------
On 6/30/24 8:53 AM, Jonas Bernoulli wrote:
What made the difference here isn't that you created a fine-grained token -- the previous token was also fine-grained, as other tokens are not supported. More likely the old token had simply expired.
—
Reply to this email directly, [view it on GitHub](#678 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACEVBUOYYPMBD7BK3RKH2E3ZKASZPAVCNFSM6AAAAABKEES2V2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMJXGY4DO).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
After some time failing to add my organization's repos with
forge-add-repository
(returned:ghub-repository-id: Repository "org/repo" does not exist on "api.github.com".
). I fixed the issue by creating a fine-grained GitHub token and clearing theauthinfo
cache.I thought this problem might affect other users, so I wanted to mention my use-case.
Thank you for magit and forge, @tarsius.
Beta Was this translation helpful? Give feedback.
All reactions