Unable to set private repo('s) back to public #269

New Issue

GiteaMirror · 2025-11-02T03:16:44-06:00

GiteaMirror commented

2025-11-02 03:16:44 -06:00

Originally created by @francoism90 on GitHub (Jan 23, 2017).

Gitea version (or commit ref): git
Git version: master
Operating system: Arch Linux
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

app.ini:

[repository]
; Force every new repository to be private
FORCE_PRIVATE             = false ; was true

Restarted the service, logged out; however every new repo will be Private instead of Public.
The Visibility toggle has no effect.

Thanks! :)

Originally created by @francoism90 on GitHub (Jan 23, 2017). - Gitea version (or commit ref): git - Git version: master - Operating system: Arch Linux - 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 app.ini: ``` [repository] ; Force every new repository to be private FORCE_PRIVATE = false ; was true ``` Restarted the service, logged out; however every new repo will be Private instead of Public. The Visibility toggle has no effect. Thanks! :)

GiteaMirror added the issue/not-a-bug label 2025-11-02 03:16:44 -06:00

GiteaMirror closed this issue

2025-11-02 03:16:44 -06:00

GiteaMirror commented

2025-11-02 03:16:45 -06:00

@lunny commented on GitHub (Jan 23, 2017):

This only effect the new repository when creating.

@lunny commented on GitHub (Jan 23, 2017): This only effect the new repository when creating.

GiteaMirror commented

2025-11-02 03:16:45 -06:00

@francoism90 commented on GitHub (Jan 23, 2017):

@lunny Correct, but now I've set FORCE_PRIVATE to false - new repo's should be public instead as private. But still every new repo is created as private and I'm unable to toggle/force it to another state.

@francoism90 commented on GitHub (Jan 23, 2017): @lunny Correct, but now I've set FORCE_PRIVATE to ```false``` - new repo's should be public instead as private. But still every new repo is created as private and I'm unable to toggle/force it to another state.

GiteaMirror commented

2025-11-02 03:16:45 -06:00

@lunny commented on GitHub (Jan 24, 2017):

I cannot reproduce this.
When set FORCE_PRIVATE = false, then

When set FORCE_PRIVATE = true, and restart Gitea,

Both are OK. I tested in master with sqlite.

@lunny commented on GitHub (Jan 24, 2017): I cannot reproduce this. When set FORCE_PRIVATE = false, then ![image](https://cloud.githubusercontent.com/assets/81045/22246745/402ff91e-e271-11e6-9d5b-a308fe58f2c9.png) When set FORCE_PRIVATE = true, and restart Gitea, ![image](https://cloud.githubusercontent.com/assets/81045/22246733/2da387c0-e271-11e6-9df8-ffad4e830062.png) Both are OK. I tested in master with sqlite.

GiteaMirror commented

2025-11-02 03:16:45 -06:00

@francoism90 commented on GitHub (Jan 24, 2017):

Never-mind, sorry for the confusion, I was editing the wrong app.ini. :/
Thanks for testing and will double-check next time!

@francoism90 commented on GitHub (Jan 24, 2017): Never-mind, sorry for the confusion, I was editing the wrong app.ini. :/ Thanks for testing and will double-check next time!

GiteaMirror referenced this issue

2025-11-02 11:42:53 -06:00

[PR #269] [MERGED] Golint fixed for modules/log #15274

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#269