github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Mark repo as NSFW #6546

New Issue
Closed
opened 2025-11-02 06:58:58 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 06:58:58 -06:00
Owner
Copy Link

Originally created by @SoniEx2 on GitHub (Dec 18, 2020).

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

Description

It'd be nice if you could mark a repo as NSFW, for projects involving NSFW topics.

Screenshots

Originally created by @SoniEx2 on GitHub (Dec 18, 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. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. 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: <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description It'd be nice if you could mark a repo as NSFW, for projects involving NSFW topics. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 06:58:58 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Dec 18, 2020):

Please feel free to use repo topics to tag your repos as such.

@techknowlogick commented on GitHub (Dec 18, 2020): Please feel free to use repo topics to tag your repos as such.
GiteaMirror commented 2025-11-02 06:58:59 -06:00
Author
Owner
Copy Link

@SoniEx2 commented on GitHub (Dec 18, 2020):

Opening a NSFW repo should require the user to click through, tho.

@SoniEx2 commented on GitHub (Dec 18, 2020): Opening a NSFW repo should require the user to click through, tho.
GiteaMirror commented 2025-11-02 06:58:59 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 18, 2020):

I guess fundamentally we are not trying to build a general purpose file repository but instead a source code repository.

Almost all content and use of content that is not safe for work is not going to be best stored within git. That is, in the majority of cases the content will be binary data that does not change and there is in no need or meaningful use of version control. In the rare cases that there actual call for version control - i.e. because there is editing, then it's likely that the content is work and an nsfw click through would just be annoying.

Whilst a PR that added such a feature might be reasonably mergable. I'm not certain we would want to, as I don't think I understand how this would all work and what it's purpose is.

@zeripath commented on GitHub (Dec 18, 2020): I guess fundamentally we are not trying to build a general purpose file repository but instead a source code repository. Almost all content and use of content that is not safe for work is not going to be best stored within git. That is, in the majority of cases the content will be binary data that does not change and there is in no need or meaningful use of version control. In the rare cases that there actual call for version control - i.e. because there is editing, then it's likely that the content is work and an nsfw click through would just be annoying. Whilst a PR that added such a feature might be reasonably mergable. I'm not certain we would want to, as I don't think I understand how this would all work and what it's purpose is.
GiteaMirror commented 2025-11-02 06:58:59 -06:00
Author
Owner
Copy Link

@SoniEx2 commented on GitHub (Dec 18, 2020):

It would be appropriate for collaborative smut, open source sex games, and whatnot. Github bans those and Gitea could provide an alternative.

@SoniEx2 commented on GitHub (Dec 18, 2020): It would be appropriate for collaborative smut, open source sex games, and whatnot. Github bans those and Gitea could provide an alternative.
GiteaMirror commented 2025-11-02 06:58:59 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Dec 18, 2020):

Since Gitea is self hostable and has options for private, public, limited visibility orgs, etc.
I also think there are plenty of ways to achieve this without an explicit NSFW filter.

@jolheiser commented on GitHub (Dec 18, 2020): Since Gitea is self hostable and has options for private, public, limited visibility orgs, etc. I also think there are plenty of ways to achieve this without an explicit NSFW filter.
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
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#6546
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?