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

[ui] the labels in issue sidebar view is too close #13545

Closed
6 tasks
a1012112796 opened this issue Nov 13, 2020 · 1 comment · Fixed by #13553
Closed
6 tasks

[ui] the labels in issue sidebar view is too close #13545

a1012112796 opened this issue Nov 13, 2020 · 1 comment · Fixed by #13553
Labels
issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself topic/ui Change the appearance of the Gitea UI type/bug
Milestone

Comments

@a1012112796
Copy link
Member

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

now:
image

suggest:
image

Screenshots

@mrsdizzie mrsdizzie added this to the 1.14.0 milestone Nov 13, 2020
@mrsdizzie mrsdizzie added type/bug issue/regression Issue needs no code to be fixed, only a description on how to fix it yourself topic/ui Change the appearance of the Gitea UI labels Nov 13, 2020
@mrsdizzie
Copy link
Member

Seems OK in 1.13, should be from more recent change

silverwind added a commit to silverwind/gitea that referenced this issue Nov 13, 2020
techknowlogick pushed a commit that referenced this issue Nov 14, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Jan 18, 2021
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 topic/ui Change the appearance of the Gitea UI type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants