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

Set private status about User (not logged) #732

New Issue
Open
opened 2025-11-02 03:34:23 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2025-11-02 03:34:23 -06:00
Owner
Copy Link

Originally created by @camlafit on GitHub (May 23, 2017).

Follow #714 issue

If any user are set in private organization, shouldn't displayed in explore/users
User should be set as private, actually looks possible to hide his email.

Should be nice to have :

  • an option to set default account visibility (public, private, connected)
  • an option on each user profil to ovveride this behavior
  • display user data following organization properties.
Originally created by @camlafit on GitHub (May 23, 2017). Follow #714 issue If any user are set in private organization, shouldn't displayed in **explore/users** User should be set as private, actually looks possible to hide his email. Should be nice to have : * an option to set default account visibility (public, private, connected) * an option on each user profil to ovveride this behavior * display user data following organization properties.
GiteaMirror added the type/featuretype/proposal labels 2025-11-02 03:34:23 -06:00
GiteaMirror commented 2025-11-02 03:34:24 -06:00
Author
Owner
Copy Link

@DblK commented on GitHub (May 23, 2017):

Once #1763 is merged, it can be done easily since organization are user in database.

  1. Add a new ini parameter and reflect in the UI
  2. Like organization, allow modification in settings
  3. Hide organizations for other members based on organization visibility and current user organizations
  4. Modify the explore/users to display according to visibibility

Hope I understand it well.

@DblK commented on GitHub (May 23, 2017): Once #1763 is merged, it can be done easily since *organization* are *user* in database. 1. Add a new ini parameter and reflect in the UI 2. Like organization, allow modification in settings 3. Hide organizations for other members based on organization visibility and current user organizations 4. Modify the explore/users to display according to visibibility Hope I understand it well.
GiteaMirror commented 2025-11-02 03:34:24 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (May 23, 2017):

Hi

Yes idea is very similar. Purpose is to hide contributor information as organization/repo done in #1763.

If we can manage organization visibility, looks logical to have same behavior with user visibility.
Thanks

@camlafit commented on GitHub (May 23, 2017): Hi Yes idea is very similar. Purpose is to hide contributor information as organization/repo done in #1763. If we can manage organization visibility, looks logical to have same behavior with user visibility. Thanks
GiteaMirror commented 2025-11-02 03:34:24 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Jun 8, 2017):

What if I'm in 2 organizations, where one is public and the other is private? Should my user be set to private or public? Users are non-exclusive members in a Organization, it doesn't make sense to have a hard link between a user and an organization IMO.

@bkcsoft commented on GitHub (Jun 8, 2017): What if I'm in 2 organizations, where one is public and the other is private? Should my user be set to private or public? Users are non-exclusive members in a Organization, it doesn't make sense to have a hard link between a user and an organization IMO.
GiteaMirror commented 2025-11-02 03:34:24 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Jun 8, 2017):

Hi

In this case user could be present on explore list and only public organization could be listed on his profile.
If use override his profile to hide then shouldn't be displayed

Purpose is no to set individually each user state if organization is private

@camlafit commented on GitHub (Jun 8, 2017): Hi In this case user could be present on explore list and only public organization could be listed on his profile. If use override his profile to hide then shouldn't be displayed Purpose is no to set individually each user state if organization is private
GiteaMirror commented 2025-11-02 03:34:24 -06:00
Author
Owner
Copy Link

@agaida commented on GitHub (Nov 21, 2017):

that would be really nice to have great.

@agaida commented on GitHub (Nov 21, 2017): that would be ~~really nice to have~~ great.
GiteaMirror commented 2025-11-02 03:34:25 -06:00
Author
Owner
Copy Link

@Spenhouet commented on GitHub (Oct 2, 2018):

Solving this issue could also solve this issue: https://github.com/go-gitea/gitea/issues/2908

@Spenhouet commented on GitHub (Oct 2, 2018): Solving this issue could also solve this issue: https://github.com/go-gitea/gitea/issues/2908
GiteaMirror commented 2025-11-02 03:34:25 -06:00
Author
Owner
Copy Link

@jscaux commented on GitHub (Mar 1, 2019):

Hereby another vote in favour of having per-user public visibility settings in explore/users.

@jscaux commented on GitHub (Mar 1, 2019): Hereby another vote in favour of having per-user public visibility settings in explore/users.
GiteaMirror commented 2025-11-02 03:34:25 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Apr 25, 2019):

Hello

as #1763 is merged, could be possible to finalize this issue ? Could be very nice to have a full private gitea instance :)

Thanks again

@camlafit commented on GitHub (Apr 25, 2019): Hello as #1763 is merged, could be possible to finalize this issue ? Could be very nice to have a full private gitea instance :) Thanks again
GiteaMirror commented 2025-11-02 03:34:25 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 25, 2019):

@camlafit I think this one is not the same as #1763 ? This is for user and that's for organization.

@lunny commented on GitHub (Apr 25, 2019): @camlafit I think this one is not the same as #1763 ? This is for user and that's for organization.
GiteaMirror commented 2025-11-02 03:34:26 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Apr 25, 2019):

Yes is not same, but follows. Now we can set repo and organization as full private , miss user management part to be complete.

As discussed with @DblK was look easier to solve this issue only after to have close #1763 .

@camlafit commented on GitHub (Apr 25, 2019): Yes is not same, but follows. Now we can set repo and organization as full private , miss user management part to be complete. As discussed with @DblK was look easier to solve this issue only after to have close #1763 .
GiteaMirror commented 2025-11-02 03:34:26 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 25, 2019):

So let's keep this open

@lunny commented on GitHub (Apr 25, 2019): So let's keep this open
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 type/feature type/proposal
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#732
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?