-
Notifications
You must be signed in to change notification settings - Fork 47
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
GitHub access token found in commit #4
Comments
By "revoke" do you actually really mean that GitHub discards the token? So we are actually talking about the token being marked as "revoke" in your GitHub settings and not that you get simply am error message because the token is invalid (if so, please post the error message here)? That's odd. The repo can be private or public. Sounds like this behavior tbh. But that would mean that you either don't have a |
Yes, discards the token. Goes away from the list of available tokens. Goes away if repo is public. That behavior would match imo. I have a .gitignore (only found with "ls -la"). Havent edited it and looks the same as yours. Seemingly works fine when i made the repo private. Weird. So maybe it's solved? Works almost perfectly now that I got past that hurdle. Just the moonraker updater klipper-backup is saying invalid and asking for soft or hard reset? Any ideas? Followed the guide |
Yeah, a private repository will work as GitHub security guidelines don't affect token from being revoked after pushing them. This only happens in public repository because of obviously reasons. But again, this is weird. Can you check your private repository on GitHub? Is the token somewhere in this repository in any file? My first guess was, that you put the token also in the .env.example (which will be pushed). It has to be somewhere. About the soft/hard reset issue: i think I now why this happens and I have a bad feeling about this. (Long story short: the GitHub repository klipper-Backup will be re-initialized with your own repository and not this one here, this will lead to exactly this error because the data in your folder is obviously different from the data in this repository - like you edit stuff in the I will look into detail in a week. The macro should work anyway, I think you can simply ignore it for the time. |
It is in .env. Nowhere else. I didn't get .env by following the guide and only got .env.example. Then I renamed that to .env and then put all that stuff in normally. Maybe it didnt change/register properly or something? How would I go about fixing that?
Your explanation makes sense. Hope you can fix it. It works for the time being so i'll just run it manually. Here is what running the script looks like. Your explanation here likely has to do with the "glut of gotchas" so I figured I'd post this. (newest at the top). Edit: Ah it makes Edit2: Am I supposed to be git pushing/pulling since I get
|
What kind of installation did you use? Sounds like this one, before i edited this wiki page a few days ago. Previously the step was cd ~
git clone https://github.com/Staubgeborener/klipper-backup
chmod +x ./klipper-backup/*.sh && ./klipper-backup/install.sh which leadsto a missing cd ~
git clone https://github.com/Staubgeborener/klipper-backup klipper-backup-main
chmod +x ./klipper-backup-main/*.sh && ./klipper-backup-main/install.sh
Actually the own backup repository should be in his own folder, which is independent from the
Never had this issue before, i can't tell you what caused this on your side. But check all modified files with a |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
When i insert github_token into .env and push by "bash script.sh" inside ~/klipper-backup in SSH, github instantly revokes my access token. Is the repo supposed to be private or something? Doesnt seem to matter if its a fine grain or normal token.
The text was updated successfully, but these errors were encountered: