github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Duplicated/empty row on My Repositories on Organization dashboard #248

New Issue
Closed
opened 2025-11-02 03:15:47 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 03:15:47 -06:00
Owner
Copy Link

Originally created by @jomp16 on GitHub (Jan 18, 2017).

  • Gitea version (or commit ref): 1.0.0+133-gd2bb8ef5
  • Git version: 2.11.0
  • Operating system: Arch Linux
  • Database (use [x]):
    • MySQL
  • Can you reproduce the bug at https://try.gitea.io:
    • No (not sure tho).

Description

I created a new organization and changed the owner of repository to that organization. That worked perfectly.

But I found something strange on Organization dashboard:

The empty row on "my repositories" just links to the Organization url.

Excepted result is:

(I removed the empty rows with Chrome inspector).

I don't know if the way I did to change ownership from me to a organization is wrong, or this is a Gitea bug.

Originally created by @jomp16 on GitHub (Jan 18, 2017). - Gitea version (or commit ref): 1.0.0+133-gd2bb8ef5 - Git version: 2.11.0 - Operating system: Arch Linux - Database (use `[x]`): - [x] MySQL - Can you reproduce the bug at https://try.gitea.io: - [x] No (not sure tho). ## Description I created a new organization and changed the owner of repository to that organization. That worked perfectly. But I found something strange on Organization dashboard: ![](http://i.imgur.com/SaO43fm.png) The empty row on "my repositories" just links to the Organization url. Excepted result is: ![](http://i.imgur.com/7HdDGAl.png) (I removed the empty rows with Chrome inspector). I don't know if the way I did to change ownership from me to a organization is wrong, or this is a Gitea bug.
GiteaMirror added the issue/duplicate label 2025-11-02 03:15:47 -06:00
GiteaMirror commented 2025-11-02 03:15:48 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 18, 2017):

Duplicate of https://github.com/go-gitea/gitea/issues/56, please try to reproduce a big first on try.gitea.io which is always running latest master.

@tboerger commented on GitHub (Jan 18, 2017): Duplicate of https://github.com/go-gitea/gitea/issues/56, please try to reproduce a big first on try.gitea.io which is always running latest master.
GiteaMirror commented 2025-11-02 03:15:48 -06:00
Author
Owner
Copy Link

@jomp16 commented on GitHub (Jan 18, 2017):

I guess I didn't ask for theme support? Maybe you linked the wrong issue number?

And I also guess try.gitea.io isn't always updated, because version: 1.0.0+116-g69b86378.

But yeah, I don't see it on try.gitea.io. Update it to latest master and I can check it again.

I'll build with commit 69b86378ce (to match try.gitea.io) and check if issue is on my side or some recent commit broke it.

--

Not a bug on my side, I build with version: 1.0.0+116-g69b86378 and it correctly show all the six repositories, without any empty <li> tag.

Did you misunderstand my issue?

--

I guess I need to find the faulty commit...

@jomp16 commented on GitHub (Jan 18, 2017): I **_guess_** I didn't ask for theme support? Maybe you linked the wrong issue number? And I also **_guess_** try.gitea.io isn't always updated, because version: 1.0.0+116-g69b86378. But yeah, I don't see it on try.gitea.io. Update it to latest master and I can check it again. I'll build with commit 69b86378cef6e4e72a563ca029a06932838484fe (to match try.gitea.io) and check if issue is on my side or some recent commit broke it. -- Not a bug on my side, I build with version: 1.0.0+116-g69b86378 and it correctly show all the six repositories, without any empty `<li>` tag. Did you misunderstand my issue? -- I guess I need to find the faulty commit...
GiteaMirror commented 2025-11-02 03:15:48 -06:00
Author
Owner
Copy Link

@jomp16 commented on GitHub (Jan 19, 2017):

I found the faulty commit: 302fa42980.

Tested the commit before that (which is 88f45ce38c) and it didn't give out empty <li> tags.

I'm not sure why this commit gives an empty <li> tags, because it never touched the template file.

Maybe this line? 302fa42980 (diff-97681c8a2932ea3c23325d3518374d98R608)

I'll revert this commit and see the results

--

Yep, reverting that commit renders the "My repositories" correctly without any extra empty <li> , but I really not sure the why.

--

@tboerger can you reopen this?

@jomp16 commented on GitHub (Jan 19, 2017): I found the faulty commit: 302fa4298008cf2e5d52d442b16c8e598551200b. Tested the commit before that (which is 88f45ce38ccc93dccb5bbffea9ff6328d7612275) and it didn't give out empty `<li>` tags. I'm not sure why this commit gives an empty `<li>` tags, because it **never** touched the template file. Maybe this line? https://github.com/go-gitea/gitea/commit/302fa4298008cf2e5d52d442b16c8e598551200b#diff-97681c8a2932ea3c23325d3518374d98R608 I'll revert this commit and see the results -- Yep, reverting that commit renders the "My repositories" correctly without any extra empty `<li>` , but I really not sure the why. -- @tboerger can you reopen this?
GiteaMirror commented 2025-11-02 03:15:48 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 19, 2017):

https://github.com/go-gitea/gitea/issues/564 is the correct issue and the referenced pull request should have fixed that.

@tboerger commented on GitHub (Jan 19, 2017): https://github.com/go-gitea/gitea/issues/564 is the correct issue and the referenced pull request should have fixed that.
GiteaMirror commented 2025-11-02 03:15:49 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 19, 2017):

And try.gitea.io is always the latest version... It shows 1.0.0 + 116 commits.

If your issue still isn't resolved please explain more details.

@tboerger commented on GitHub (Jan 19, 2017): And try.gitea.io is always the latest version... It shows 1.0.0 + 116 commits. If your issue still isn't resolved please explain more details.
GiteaMirror commented 2025-11-02 03:15:49 -06:00
Author
Owner
Copy Link

@jomp16 commented on GitHub (Jan 19, 2017):

You sure? Because seems try.gitea.io is at version 1.0.0+116-g69b86378.

See the commit after the g and search GitHub commits for that commit.
Commit: 69b8637 name: "docs: update zh-tw translation".

See how many new commits Gitea team have made (16 new commits), and the the
commit that is faulty for me, is in the middle of the new commits.

So... Update try.gitea.io to point to the literally latest master which
is d2bb8ef5 name: "Notifications: trying to get a better layout". And
I'll check again.

Ping @lunny, because you made that commit that's supposed to fix. But for
some reason it does not for me. Reverting that commit does not generate
empty lines alongside of the repositories links. See the first image on
issue.

Maybe I should record or create a test user and Organization on my
Gitea instance running latest master and you see by yourselves?

@jomp16 commented on GitHub (Jan 19, 2017): You sure? Because seems try.gitea.io is at version 1.0.0+116-g69b86378. See the commit after the g and search GitHub commits for that commit. Commit: 69b8637 name: "docs: update zh-tw translation". See how many new commits Gitea team have made (16 new commits), and the the commit that is faulty for me, is in the middle of the new commits. So... Update try.gitea.io to point to the literally latest master which is d2bb8ef5 name: "Notifications: trying to get a better layout". And I'll check again. Ping @lunny, because you made that commit that's supposed to fix. But for some reason it does not for me. Reverting that commit does not generate empty lines alongside of the repositories links. See the first image on issue. Maybe I should record or create a test user and Organization on my Gitea instance running latest master and you see by yourselves?
GiteaMirror commented 2025-11-02 03:15:49 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 19, 2017):

try.gitea.io seems not the latest version. It's 1.0.0+116-g69b86378, but it should 1.0.0+134-g3c4d5e1e.

@lunny commented on GitHub (Jan 19, 2017): `try.gitea.io` seems not the latest version. It's `1.0.0+116-g69b86378`, but it should `1.0.0+134-g3c4d5e1e`.
GiteaMirror commented 2025-11-02 03:15:49 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Jan 20, 2017):

^ I've noticed that try. isn't always updated as well, though I assumed it was drone being slow on the builds...

@bkcsoft commented on GitHub (Jan 20, 2017): ^ I've noticed that `try.` isn't always updated as well, though I assumed it was drone being slow on the builds...
GiteaMirror commented 2025-11-02 03:15:50 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 20, 2017):

@tboerger

@lunny commented on GitHub (Jan 20, 2017): @tboerger
GiteaMirror commented 2025-11-02 03:15:50 -06:00
Author
Owner
Copy Link

@jomp16 commented on GitHub (Jan 25, 2017):

And since try.gitea.io is updated (1.0.0+149-g8bc43195). I can reproduce this bug on it.

http://i.imgur.com/XHg2PyK.png

@tboerger now reopen this. You can reproduce this bug by switching to Organization on Dashboard. Like I said.

All teh info is on comments above.

@jomp16 commented on GitHub (Jan 25, 2017): And since try.gitea.io is updated (1.0.0+149-g8bc43195). I **can** reproduce this bug on it. http://i.imgur.com/XHg2PyK.png @tboerger now reopen this. You can reproduce this bug by switching to Organization on Dashboard. Like I said. All teh info is on comments above.
GiteaMirror commented 2025-11-02 03:15:50 -06:00
Author
Owner
Copy Link

@Bwko commented on GitHub (Jan 25, 2017):

Possible duplicate of #746?

@Bwko commented on GitHub (Jan 25, 2017): Possible duplicate of #746?
GiteaMirror commented 2025-11-02 03:15:51 -06:00
Author
Owner
Copy Link

@jomp16 commented on GitHub (Jan 25, 2017):

Possible, but I reported first, and nobody believed me :)

Anyways, if it's a known issue now. Good :)

@jomp16 commented on GitHub (Jan 25, 2017): Possible, but I reported first, and nobody believed me :) Anyways, if it's a known issue now. Good :)
GiteaMirror commented 2025-11-02 03:15:51 -06:00
Author
Owner
Copy Link

@Bwko commented on GitHub (Jan 25, 2017):

@jomp16 I agree #746 is a duplicate of this issue 😉
Could you test if #749 solves your issue?

@Bwko commented on GitHub (Jan 25, 2017): @jomp16 I agree #746 is a duplicate of this issue :wink: Could you test if #749 solves your issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#248
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?