-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Option to init empty wiki Git remote repository upon repository creation #7226
Comments
Bonus... if there is no bug (LOL), when you migrate/mirror a repository, Gogs would make an attempt to see if |
Oh right, I think you’d have to create a first page until the UI could be shown (at when the remote wiki Git repo is created). Once the remote wiki Git repo is created on the server side, a force push might do the trick? |
Yes. It worked. I don't know the --force option. Thanks! |
Not a bad idea, just to clarify, the intended improvement is: Give an option to also init wiki Git repo at the main repo creation? (in that case you can start push your existing wiki, just like pushing an existing local repo to an empty remote repo) |
Yes! That would be great :) Thanks! |
This fixes github issue gogs#7226
Describe the feature
Hello,
On GitHub, there is this feature that for a given repo, its regular git url is repo.git, but the wiki is available at repo.wiki.git (on the GUI: "Clone this wiki locally")
Is there a way to implement that on Gogs?
Thanks!
Describe the solution you'd like
In the same way I pull my regular code from repo.git, I'd like to pull my wiki from repo.wiki.git
Describe alternatives you've considered
I can still create a specific wiki git repository, but I am not sure there is a way to make the wiki work with Gogs... What would the external URL be? How would people be able to change the wiki so that it is reflected in the wiki git repo?
It could also be a specific branch in the main repo, but that would be hard to reconcile with repositories that are mirrored on both GitHub and Gogs (yes, I have those)
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: