github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-10 16:44:50 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Feature Request: Ability to mark Organization as private #2926

New Issue
Closed
opened 2025-11-02 04:54:21 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 04:54:21 -06:00
Owner
Copy Link

Originally created by @bkraul on GitHub (Feb 16, 2019).

  • 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
    • Not relevant
  • Log gist:

Description

The ability to mark organizations private so that they will not show in the explore section for non-logged in users (if the site allows public viewing) or users that do not belong to the particular organization, would be nice. This is already set at the repository level, but it would be nice to have that option at the organization level.

Originally created by @bkraul on GitHub (Feb 16, 2019). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) 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): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description The ability to mark organizations private so that they will not show in the explore section for non-logged in users (if the site allows public viewing) or users that do not belong to the particular organization, would be nice. This is already set at the repository level, but it would be nice to have that option at the organization level.
GiteaMirror added the issue/duplicate label 2025-11-02 04:54:21 -06:00
GiteaMirror commented 2025-11-02 04:54:22 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Feb 16, 2019):

Closed as duplicate. I’m afraid I’m on mobile right now so I can’t find the ticket number, but a PR for this is in 1.8 milestone

@techknowlogick commented on GitHub (Feb 16, 2019): Closed as duplicate. I’m afraid I’m on mobile right now so I can’t find the ticket number, but a PR for this is in 1.8 milestone
GiteaMirror commented 2025-11-02 04:54:22 -06:00
Author
Owner
Copy Link

@bkraul commented on GitHub (Feb 16, 2019):

Tracked on #714 PR #1763

@bkraul commented on GitHub (Feb 16, 2019): Tracked on #714 PR #1763
GiteaMirror commented 2025-11-02 04:54:22 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Feb 16, 2019):

Thanks for linking :)

@techknowlogick commented on GitHub (Feb 16, 2019): Thanks for linking :)
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#2926
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?