Feature Request: keeping repo and wiki together #2608

New Issue

GiteaMirror · 2025-11-02T04:41:55-06:00

GiteaMirror commented

2025-11-02 04:41:55 -06:00

Originally created by @4001982248998 on GitHub (Dec 4, 2018).

When transferring a repo with wiki to a second Gitea server, it would be nice to be able to somehow include the wiki in the cloned repository.

There currently is no option to import the wiki from the repository origin, or even synchronize the wikis.

Originally created by @4001982248998 on GitHub (Dec 4, 2018). When transferring a repo with wiki to a second Gitea server, it would be nice to be able to somehow include the wiki in the cloned repository. There currently is no option to import the wiki from the repository origin, or even synchronize the wikis.

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:41:55 -06:00

GiteaMirror closed this issue

2025-11-02 04:41:55 -06:00

GiteaMirror commented

2025-11-02 04:41:56 -06:00

@jsfaint commented on GitHub (Jan 4, 2019):

You can create a 'New Miragtion' in the target gitea
When mirage repo from outside(github/gitea), gitea will mirage the wiki too.

@jsfaint commented on GitHub (Jan 4, 2019): You can create a 'New Miragtion' in the target gitea When mirage repo from outside(github/gitea), gitea will mirage the wiki too.

GiteaMirror commented

2025-11-02 04:41:56 -06:00

@4001982248998 commented on GitHub (Jan 4, 2019):

thank you, @jsfaint ! This unfortunately does only work when there is a direct connection between the two hosts. In my case we are working with a SSH tunnel setup.

@4001982248998 commented on GitHub (Jan 4, 2019): thank you, @jsfaint ! This unfortunately does only work when there is a direct connection between the two hosts. In my case we are working with a SSH tunnel setup.

GiteaMirror commented

2025-11-02 04:41:57 -06:00

@jsfaint commented on GitHub (Jan 5, 2019):

@4001982248998 emm, got it. It looks like you need access remote gitea server via proxy.
I'm not sure if environment variables http_proxy, https_proxy and socks_proxy works for this case.
Set these environment variables for local gitea server, then create new migration.

@jsfaint commented on GitHub (Jan 5, 2019): @4001982248998 emm, got it. It looks like you need access remote gitea server via proxy. I'm not sure if environment variables `http_proxy`, `https_proxy` and `socks_proxy` works for this case. Set these environment variables for local gitea server, then create new migration.

GiteaMirror commented

2025-11-02 04:41:57 -06:00

@stale[bot] commented on GitHub (Mar 6, 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 (Mar 6, 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 04:41:57 -06:00

@lunny commented on GitHub (Jan 28, 2020):

I think we have done this. Please feel free to reopen it.

@lunny commented on GitHub (Jan 28, 2020): I think we have done this. Please feel free to reopen it.

GiteaMirror referenced this issue

2025-11-02 12:12:08 -06:00

[PR #2608] [CLOSED] [CHANGELOG] Drop redundant OpenID items #16503

Sign in to join this conversation.