# How to mirror private GitHub repositories

**URL:** <https://forum.gitea.com/t/how-to-mirror-private-github-repositories/198>\
**Category:** Install/Maintain/Configure\
**Created:** [February 4, 2018, 12:58pm UTC](https://forum.gitea.com/t/how-to-mirror-private-github-repositories/198 "2018-02-04T12:58:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kekub](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@kekub](https://forum.gitea.com/u/kekub)\
**Post date:** [February 4, 2018, 12:58pm UTC](https://forum.gitea.com/t/how-to-mirror-private-github-repositories/198/1 "2018-02-04T12:58:14Z")

</div>

I am in the process of transitioning all my repositories at GitHub to my private Gitea instance. So far everything went pretty good. However I am not able to find any hints on how to mirror my  
_private_ repositories at GitHub with Gitea. Is this even possible?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![cez81](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/cez81/32/123_2.png) [@cez81](https://forum.gitea.com/u/cez81)\
**Post date:** [February 7, 2018, 11:13am UTC](https://forum.gitea.com/t/how-to-mirror-private-github-repositories/198/2 "2018-02-07T11:13:43Z")

</div>

I don’t have any private repositories to test with but I guess you could use the “Need Authorization” option when migrating?

---

<div class="post-metadata">

**Author:** ![howl](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/howl/32/4725_2.png) [@howl](https://forum.gitea.com/u/howl)\
**Post date:** [February 26, 2018, 5:57pm UTC](https://forum.gitea.com/t/how-to-mirror-private-github-repositories/198/3 "2018-02-26T17:57:51Z")

</div>

As @cez81 said, you can use the Need Authorization settings, and set your username and password as the parameters. Or if you don’t want to write your password, you can use a [GitHub personal access token](https://github.com/settings/tokens):

> Personal access tokens function like ordinary OAuth access tokens. They can be used instead of a password for Git over HTTPS […]
