Fine grained PAT Expired After Pushing a File Containing the PAT to a Public Repo #150205
Unanswered
AkinduID
asked this question in
New to GitHub
Replies: 1 comment 1 reply
-
|
Hey @AkinduID, Yeah, that’s exactly why your PAT got revoked. GitHub has automatic secret scanning, and if it detects a token in a public repo, it immediately disables it for security reasons. Even if you bypass push protection, GitHub still invalidates the token. To avoid this in the future: Never push secrets to a repo (even private ones). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I created a fine-grained Personal Access Token (PAT) for testing, set to expire in a year. However, it expired unexpectedly.
I tried pushing a branch that contained a file with the PAT to a public repository. After bypassing push protection to expose the token, I was able to push successfully. Could this have caused the token to expire? Any help would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions