We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2.6.0
Linux
NixOS 24.11
Other - please describe below
gitea via oidc
None
Yes, I can access the repository
GCM should execute my git command without failing
e.g. git push -> exit code 0
My git command fails and only succeeds when I retry it. This issue is intermittent, i.e. it probably is related to OIDC token refresh or libsecret.
❯ git push remote: Verify fatal: Authentication failed for 'https://XXXXXXX' ❯ git push Enumerating objects: 11, done. Counting objects: 100% (11/11), done. Delta compression using up to 12 threads Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 628 bytes | 628.00 KiB/s, done. Total 6 (delta 3), reused 0 (delta 0), pack-reused 0 (from 0) remote: . Processing 1 references remote: Processed 1 references in total To XXXXXX 8c477eb..55b2799 main -> main
I will attach some logs as soon as I run into the error again
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Version
2.6.0
Operating system
Linux
OS version or distribution
NixOS 24.11
Git hosting provider(s)
Other - please describe below
Other hosting provider
gitea via oidc
(Azure DevOps only) What format is your remote URL?
None
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
GCM should execute my git command without failing
e.g. git push -> exit code 0
Actual behavior
My git command fails and only succeeds when I retry it.
This issue is intermittent, i.e. it probably is related to OIDC token refresh or libsecret.
Logs
I will attach some logs as soon as I run into the error again
The text was updated successfully, but these errors were encountered: