-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create git-daemon-export-ok file when creating public repositories #15521
Comments
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
So there are a number of issues here - for a start we need to only create these files only when the repository is actually publicly viewable so the current code is likely incorrect too. |
Somewhere along the line the creation of git-daemon-export-ok files disappeared but the updating of these files when repo visibility changes remained. The problem is that the current state will create files even when the org or user is private. This PR restores creation correctly. Fix go-gitea#15521 Signed-off-by: Andrew Thornton <art27@cantab.net>
Somewhere along the line the creation of git-daemon-export-ok files disappeared but the updating of these files when repo visibility changes remained. The problem is that the current state will create files even when the org or user is private. This PR restores creation correctly. Fix #15521 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport go-gitea#16508 Somewhere along the line the creation of git-daemon-export-ok files disappeared but the updating of these files when repo visibility changes remained. The problem is that the current state will create files even when the org or user is private. This PR restores creation correctly. Fix go-gitea#15521 Signed-off-by: Andrew Thornton <art27@cantab.net>
Backport #16508 Somewhere along the line the creation of git-daemon-export-ok files disappeared but the updating of these files when repo visibility changes remained. The problem is that the current state will create files even when the org or user is private. This PR restores creation correctly. Fix #15521 Signed-off-by: Andrew Thornton <art27@cantab.net>
Somewhere along the line the creation of git-daemon-export-ok files disappeared but the updating of these files when repo visibility changes remained. The problem is that the current state will create files even when the org or user is private. This PR restores creation correctly. Fix go-gitea#15521 Signed-off-by: Andrew Thornton <art27@cantab.net>
[x]
):Description
gitea appears to have support to create the git-daemon-export-ok file when the repository is changed from private to public (done in the updateRepository() function). However, gitea does not create this file when creating a repository (either via New or Migrate options).
I can get gitea to create the git-daemon-export-ok file as I desire after creating a new repository by changing it from public to private, saving the settings, and then changing it from private back to public.
gitea should create the git-daemon-export-ok file when creating a repository if it is set to public visibility to match what is done when changing from private to public.
The text was updated successfully, but these errors were encountered: