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

Visibility option when creating a repo is misleading #361

New Issue
Closed
opened 2025-11-02 03:20:09 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 03:20:09 -06:00
Owner
Copy Link

Originally created by @sstine on GitHub (Feb 17, 2017).

  • Gitea version (or commit ref): 1.0.0+280-g0642cb33
  • Git version: 2.9.3
  • Operating system: alpine:3.4
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

The UI is a little misleading when it comes to selecting whether your repo should be private or public. It says "This repository is private" and the checkbox is a boolean on that statement, but to the user it looks like the UI is saying that the repo is private (even if the box is unchecked). This surprises the user when the repo they create is actually public. It would be more clear to take the approach that Github uses (screenshot below).

Screenshots

image

Proposed solution:
image

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @sstine on GitHub (Feb 17, 2017). - Gitea version (or commit ref): 1.0.0+280-g0642cb33 - Git version: 2.9.3 - Operating system: alpine:3.4 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description The UI is a little misleading when it comes to selecting whether your repo should be private or public. It says "This repository is private" and the checkbox is a boolean on that statement, but to the user it looks like the UI is saying that the repo is private (even if the box is unchecked). This surprises the user when the repo they create is actually public. It would be more clear to take the approach that Github uses (screenshot below). ## Screenshots ![image](https://cloud.githubusercontent.com/assets/1295911/23085053/487c0d72-f51a-11e6-9344-c0f12fd862d8.png) **Proposed solution:** ![image](https://cloud.githubusercontent.com/assets/1295911/23085150/cf3e81e6-f51a-11e6-8aca-26b070a750c9.png) <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42162663-visibility-option-when-creating-a-repo-is-misleading?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 03:20:09 -06:00
GiteaMirror commented 2025-11-02 03:20:11 -06:00
Author
Owner
Copy Link

@wrouesnel commented on GitHub (Feb 20, 2017):

It's also not clear what this does with organization memberships. It seems that unless I check "visibility", organization members can't see or access the repo.

@wrouesnel commented on GitHub (Feb 20, 2017): It's also not clear what this does with organization memberships. It seems that unless I check "visibility", organization members can't see or access the repo.
GiteaMirror commented 2025-11-02 03:20:11 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 15, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 15, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 03:20:11 -06:00
Author
Owner
Copy Link

@denyskon commented on GitHub (Apr 11, 2025):

Image

Closing as issue no longer present.

@denyskon commented on GitHub (Apr 11, 2025): ![Image](https://github.com/user-attachments/assets/9308127e-ba5c-46d4-876b-79fc28a51544) Closing as issue no longer present.
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/confirmed type/enhancement
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#361
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?