remove visibility text #11183

New Issue

2025-11-02T09:30:05-06:00

GiteaMirror commented

2025-11-02 09:30:05 -06:00

Originally created by @hiifong on GitHub (Jul 7, 2023).

Feature Description

I think the display visibility text is redundant, it would be better to replace it with follow button.

Screenshots

No response

Originally created by @hiifong on GitHub (Jul 7, 2023). ### Feature Description I think the display visibility text is redundant, it would be better to replace it with follow button. ![image](https://github.com/go-gitea/gitea/assets/89133723/9895ed9b-7911-407b-a370-27cf5d7ea76b) ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 09:30:05 -06:00

GiteaMirror commented

2025-11-02 09:30:05 -06:00

@silverwind commented on GitHub (Jul 7, 2023):

Hmm I don't quite understand the relation between "Visibility" and "Follow".

@silverwind commented on GitHub (Jul 7, 2023): Hmm I don't quite understand the relation between "Visibility" and "Follow".

GiteaMirror commented

2025-11-02 09:30:05 -06:00

@hiifong commented on GitHub (Jul 7, 2023):

Hmm I don't quite understand the relation between "Visibility" and "Follow".

If you are not a member of this org, then the members of this org set his visibility to public, we can naturally see him in this org, if not we can't see it either.

@hiifong commented on GitHub (Jul 7, 2023): > Hmm I don't quite understand the relation between "Visibility" and "Follow". If you are not a member of this org, then the members of this org set his visibility to public, we can naturally see him in this org, if not we can't see it either.

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@hiifong commented on GitHub (Jul 7, 2023):

Hmm I don't quite understand the relation between "Visibility" and "Follow".

like github:

@hiifong commented on GitHub (Jul 7, 2023): > Hmm I don't quite understand the relation between "Visibility" and "Follow". like github: ![image](https://github.com/go-gitea/gitea/assets/89133723/6f15bf52-1ac5-4b20-bb05-7df4baf391ac)

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@silverwind commented on GitHub (Jul 8, 2023):

I guess it's a good cleanup to remove this.

@silverwind commented on GitHub (Jul 8, 2023): I guess it's a good cleanup to remove this.

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@denyskon commented on GitHub (Jul 8, 2023):

I'm reworking that list currently as part of refactoring to an enhanced card style. I'll post my current state later and then we can talk about what we remove or add 🙂

@denyskon commented on GitHub (Jul 8, 2023): I'm reworking that list currently as part of refactoring to an enhanced card style. I'll post my current state later and then we can talk about what we remove or add 🙂

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@puni9869 commented on GitHub (Jul 8, 2023):

Are you doing it in an existing PR or will create a new PR for this change?

Ps: I would recommend you to go with a fresh Pr. Easy to review and maintain.

@puni9869 commented on GitHub (Jul 8, 2023): Are you doing it in an existing PR or will create a new PR for this change? Ps: I would recommend you to go with a fresh Pr. Easy to review and maintain.

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@puni9869 commented on GitHub (Jul 8, 2023):

I'm reworking that list currently as part of refactoring to an enhanced card style. I'll post my current state later and then we can talk about what we remove or add 🙂

on @denyskon comment

Are you doing it in an existing PR or will create a new PR for this change?

Ps: I would recommend you to go with a fresh Pr. Easy to review and maintain.

@hiifong

@puni9869 commented on GitHub (Jul 8, 2023): > I'm reworking that list currently as part of refactoring to an enhanced card style. I'll post my current state later and then we can talk about what we remove or add 🙂 on @denyskon comment Are you doing it in an existing PR or will create a new PR for this change? Ps: I would recommend you to go with a fresh Pr. Easy to review and maintain. @hiifong

GiteaMirror commented

2025-11-02 09:30:06 -06:00

@denyskon commented on GitHub (Jul 8, 2023):

I don't intend to change the functionality in my PR, it's only about layout/styling. We can add the follow button later in a separate PR.

@denyskon commented on GitHub (Jul 8, 2023): I don't intend to change the functionality in my PR, it's only about layout/styling. We can add the follow button later in a separate PR.

GiteaMirror commented

2025-11-02 09:30:07 -06:00

@denyskon commented on GitHub (Jul 8, 2023):

regular member

owner

regular user/guest

@denyskon commented on GitHub (Jul 8, 2023): #### regular member ![Bildschirmfoto vom 2023-07-08 19-54-37](https://github.com/go-gitea/gitea/assets/47871822/aebe4fe0-f614-46da-b8c1-1a547a149d8e) #### owner ![Bildschirmfoto vom 2023-07-08 19-54-02](https://github.com/go-gitea/gitea/assets/47871822/cd044572-9e92-4d4a-8702-7b8b8320e5b4) #### regular user/guest ![Bildschirmfoto vom 2023-07-08 19-51-07](https://github.com/go-gitea/gitea/assets/47871822/9f10eaa7-a9b8-49d1-8c2e-45f00b0e7852)

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#11183