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

Visual cue for Organization with Visibility Limited + Private #6084

New Issue
Closed
opened 2025-11-02 06:44:43 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 06:44:43 -06:00
Owner
Copy Link

Originally created by @aschrijver on GitHub (Oct 2, 2020).

  • Gitea version (or commit ref): master

Description

There is no visual indicator that an Organization has Visibility set to Limited or Private. Only when going to Settings this becomes apparent. There should be a visual cue (an icon or label) on the organization page and in the organization list on the dashboard.

Background info

This caused confusion with me, and I reported an OpenGraph bug to Codeberg (No Discourse onebox when pasting links, and OpenGraph checker gave me 404 error). However, I forgot that upon creation I had set my org to be Limited visible, and afterwards never noticed this was still the case.

Originally created by @aschrijver on GitHub (Oct 2, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): `master` ## Description There is no visual indicator that an Organization has Visibility set to Limited or Private. Only when going to Settings this becomes apparent. There should be a visual cue (an icon or label) on the organization page and in the organization list on the dashboard. ### Background info This caused confusion with me, and I reported an OpenGraph bug to [Codeberg](https://codeberg.org/Codeberg/Community/issues/256#issuecomment-95120) (No Discourse onebox when pasting links, and OpenGraph checker gave me 404 error). However, I forgot that upon creation I had set my org to be Limited visible, and afterwards never noticed this was still the case.
GiteaMirror added the hacktoberfesttopic/uigood first issue labels 2025-11-02 06:44:43 -06:00
GiteaMirror commented 2025-11-02 06:44:44 -06:00
Author
Owner
Copy Link

@spenaustin commented on GitHub (Oct 3, 2020):

I'd be interested in trying this one. I'm admittedly not a UX expert -- do you think the best way to do this would be to put labels next to the Organization name in the places mentioned above (similar to the label display on this page)? Open to any ideas.

@spenaustin commented on GitHub (Oct 3, 2020): I'd be interested in trying this one. I'm admittedly not a UX expert -- do you think the best way to do this would be to put labels next to the Organization name in the places mentioned above (similar to the label display on this page)? Open to any ideas.
GiteaMirror commented 2025-11-02 06:44:45 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Oct 3, 2020):

@smtaylorslc yeah, similar to how it is on repos would be great!

@techknowlogick commented on GitHub (Oct 3, 2020): @smtaylorslc yeah, similar to how it is on repos would be great!
GiteaMirror commented 2025-11-02 06:44:45 -06:00
Author
Owner
Copy Link

@spenaustin commented on GitHub (Oct 4, 2020):

@techknowlogick great! I've started on this and things are looking promising -- however, I don't think there's a shortened descriptor for "Visibility" in the locales (for instance, the US locale file sets settings.visibility.limited to Limited (Visible to logged in users only)). Should I add visibility shortnames to the English .ini file and have future translations for the short name be another ticket?

(apologies if these are pretty simple questions -- I'm very new to this project & open source in general!)

@spenaustin commented on GitHub (Oct 4, 2020): @techknowlogick great! I've started on this and things are looking promising -- however, I don't think there's a shortened descriptor for "Visibility" in the locales (for instance, [the US locale file](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini#L1871) sets `settings.visibility.limited` to `Limited (Visible to logged in users only)`). Should I add visibility shortnames to the English .ini file and have future translations for the short name be another ticket? (apologies if these are pretty simple questions -- I'm very new to this project & open source in general!)
GiteaMirror commented 2025-11-02 06:44:45 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 5, 2020):

yeah just add another item to the locale file. Crowdin will pick it up and translators will translate.

Speaking of which I should do a check up on crowdin...

@zeripath commented on GitHub (Oct 5, 2020): yeah just add another item to the locale file. Crowdin will pick it up and translators will translate. Speaking of which I should do a check up on crowdin...
GiteaMirror commented 2025-11-02 06:44:45 -06:00
Author
Owner
Copy Link

@spenaustin commented on GitHub (Oct 6, 2020):

Implemented in #13040 .

@spenaustin commented on GitHub (Oct 6, 2020): Implemented in #13040 .
GiteaMirror commented 2025-11-02 06:44:45 -06:00
Author
Owner
Copy Link

@aschrijver commented on GitHub (Oct 6, 2020):

Super! You rock 👍

@aschrijver commented on GitHub (Oct 6, 2020): Super! You rock 👍
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 good first issue hacktoberfest topic/ui
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#6084
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?