Skip to content
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

Error message broken when migrating repo at max repo limit #18122

Closed
SamWhited opened this issue Dec 29, 2021 · 0 comments · Fixed by #18135
Closed

Error message broken when migrating repo at max repo limit #18122

SamWhited opened this issue Dec 29, 2021 · 0 comments · Fixed by #18135
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself type/bug
Milestone

Comments

@SamWhited
Copy link

Gitea Version

1.15.6

Git Version

No response

Operating System

FreeBSD 13

How are you running Gitea?

Using Gitea from the FreeBSD repos.

Database

PostgreSQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

When you have reached your max repo limit if you attempt to migrate a repo there is no error message indicating that it can't be done. When you actually press the migrate button an error pops up, but the formatting is broken:

form.reach_limit_of_creation%!(EXTRA int=0)

Screenshots

A screenshot showing the described error message

Gusted pushed a commit to Gusted/gitea that referenced this issue Dec 30, 2021
@delvh delvh added type/bug issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself labels Dec 30, 2021
@delvh delvh added this to the 1.16.0 milestone Dec 30, 2021
lunny added a commit that referenced this issue Dec 31, 2021
- Resolves #18122

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Chianina pushed a commit to Chianina/gitea that referenced this issue Mar 28, 2022
- Resolves go-gitea#18122

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants