Provide more detailed error information for 'Push to Create not enabled'. #11714

New Issue

GiteaMirror · 2025-11-02T09:45:37-06:00

GiteaMirror commented

2025-11-02 09:45:37 -06:00

Originally created by @LamGC on GitHub (Sep 24, 2023).

Feature Description

In version 1.20.4, if a user pushes a non-existent repository, Gitea will return the following error message:

This error message is a bit difficult to understand. After encountering this issue, I needed to consult the documentation to understand the Push to create function before understanding this error message.

I hope this error message not only reminds the user that the server has not enabled the Push to Create function, but also reminds the user maybe that the current remote address has invalidated, reducing the time required for troubleshooting errors.

Screenshots

No response

Originally created by @LamGC on GitHub (Sep 24, 2023). ### Feature Description In version 1.20.4, if a user pushes a non-existent repository, Gitea will return the following error message: ![image](https://github.com/go-gitea/gitea/assets/16975255/5e7e29af-6771-45da-8343-8573df96f191) This error message is a bit difficult to understand. After encountering this issue, I needed to consult the documentation to understand the Push to create function before understanding this error message. I hope this error message not only reminds the user that the server has not enabled the Push to Create function, but also reminds the user maybe that the current remote address has invalidated, reducing the time required for troubleshooting errors. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 09:45:37 -06:00

GiteaMirror closed this issue

2025-11-02 09:45:37 -06:00

GiteaMirror commented

2025-11-02 09:45:38 -06:00

@lunny commented on GitHub (Sep 25, 2023):

So what's the real reason in your case?

@lunny commented on GitHub (Sep 25, 2023): So what's the real reason in your case?

GiteaMirror commented

2025-11-02 09:45:38 -06:00

@LamGC commented on GitHub (Sep 25, 2023):

Just because the name of the repository was changed a long time ago without changing the remote address of the local repository.😂

From: Lunny Xiao @.>
Sent: Monday, September 25, 2023 9:07:47 AM
To: go-gitea/gitea @.>
Cc: GC Lam @.>; Author @.>
Subject: Re: [go-gitea/gitea] Provide more detailed error information for 'Push to Create not enabled'. (Issue #27229)

So what's the real reason in your case?

—
Reply to this email directly, view it on GitHubhttps://github.com/go-gitea/gitea/issues/27229#issuecomment-1732751592, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEBQLF4COBCUKPEMQW6FCUDX4DKOHANCNFSM6AAAAAA5E6V7BQ.
You are receiving this because you authored the thread.Message ID: @.***>

@LamGC commented on GitHub (Sep 25, 2023): Just because the name of the repository was changed a long time ago without changing the remote address of the local repository.😂 ________________________________ From: Lunny Xiao ***@***.***> Sent: Monday, September 25, 2023 9:07:47 AM To: go-gitea/gitea ***@***.***> Cc: GC Lam ***@***.***>; Author ***@***.***> Subject: Re: [go-gitea/gitea] Provide more detailed error information for 'Push to Create not enabled'. (Issue #27229) So what's the real reason in your case? — Reply to this email directly, view it on GitHub<https://github.com/go-gitea/gitea/issues/27229#issuecomment-1732751592>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEBQLF4COBCUKPEMQW6FCUDX4DKOHANCNFSM6AAAAAA5E6V7BQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

GiteaMirror commented

2025-11-02 09:45:38 -06:00

@lng2020 commented on GitHub (Sep 25, 2023):

The error message sounds reasonable to me. Note that Please make sure you have the correct access rights and the repository exists. In your case, it's the repository does not exist.

@lng2020 commented on GitHub (Sep 25, 2023): The error message sounds reasonable to me. Note that `Please make sure you have the correct access rights and the repository exists`. In your case, it's the repository does not exist.

GiteaMirror commented

2025-11-02 09:45:39 -06:00

@LamGC commented on GitHub (Sep 25, 2023):

The error message sounds reasonable to me. Note that Please make sure you have the correct access rights and the repository exists. In your case, it's the repository does not exist.

Indeed, the information provided by Git at the bottom has already reminded me of this.

I don't know why, I always think it's not a real reason, I only focus on the error message returned by the server.

(Perhaps I have encountered such a situation before? I have already forgotten)

@LamGC commented on GitHub (Sep 25, 2023): > The error message sounds reasonable to me. Note that `Please make sure you have the correct access rights and the repository exists`. In your case, it's the repository does not exist. Indeed, the information provided by Git at the bottom has already reminded me of this. I don't know why, I always think it's not a real reason, I only focus on the error message returned by the server. (Perhaps I have encountered such a situation before? I have already forgotten)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11714