git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Failing to push to a repository erases authentication helper credentials

From
Michal Suchánek <msuchanek@suse.de>
Date
Jul 3, 2025, 10:44 UTC
Message-ID
<aGZfFNRvDlFLvlBm@kitsune.suse.cz>
In-Reply-To
<xmqqjz4rly5a.fsf@gitster.g>
On Tue, Jul 01, 2025 at 08:38:09AM -0700, Junio C Hamano wrote:
Show 8 quoted lines
> Michal Suchánek <msuchanek@suse.de> writes:
> 
> > Is there any way to see what the server is returning?
> 
> If this is going over http(s)://, then
> 
>     export GIT_TRACE_CURL=true
> 

With that I can see that the forge instance in question reports indiscriminately 401 while their demo site running the current development code correctly returns 403.

Probably a case for upgrading to a more recent version.
Thanks
Michal
Previous: Junio C Hamano
Message 8 of 8 in “Failing to push to a repository erases authentication helper credentials”
  1. Michal SuchánekJun 30, 2025
  2. brian m. carlsonJun 30, 2025
  3. Michal SuchánekJun 30, 2025
  4. brian m. carlsonJun 30, 2025
  5. Michal SuchánekJul 1, 2025
  6. Michal SuchánekJul 1, 2025
  7. Junio C HamanoJul 1, 2025
  8. Michal SuchánekJul 3, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.