-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
feature: support gpg sign commit and tags #4
Comments
I'm new using GitHub and I'm having trouble cloning my repository because the credentials are giving me an error. I don't know if I'm doing something wrong but I tried using username and password, then I tried with a personal access token and it doesn't work. It says "Error: too many redirects or authentication replays. |
1 check your repo in puppygit, make sure it linked to your credential, and make sure your github username and personal token is correct 2 check your personal token on github, if you use fine-grained token, you need choose your repo and set the content permission to read+write. |
SOLVED! The problem was related to the path of the repo. It didn't allow me to choose a different path than the one that comes by default even when I grant permissions to my storage. Anyway, it's working now. Thank you for answer! |
Commenting to request this feature! It would be very nice, as many of my repos are configured to verify every commit via checking signatures. |
I do not need this. My use case is git on my phone for private repos. I don't expect to be commiting to public repos that need verified commits. Certainly would be a neat feature to have. |
RE signing in general, rather than gpg, I can recommend https://soatok.blog/2024/11/15/what-to-use-instead-of-pgp/ (which recommends ssh signatures instead) |
I considering try support gpg sign/verify the commit and tag, but I don't need this feature, if you need, leave a comment , if have many users need, I'll try implement it.
The text was updated successfully, but these errors were encountered: