# Upgrading private Github repositories

**URL:** https://meta.discourse.org/t/upgrading-private-github-repositories/141597
**Category:** Support
**Created:** [February 14, 2020, 11:12am UTC](https://meta.discourse.org/t/upgrading-private-github-repositories/141597 "2020-02-14T11:12:36Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Varsii](https://avatars.discourse-cdn.com/v4/letter/v/bc79bd/32.png) [@Varsii](https://meta.discourse.org/u/Varsii)
#### Post date: [February 14, 2020, 11:12am UTC](https://meta.discourse.org/t/upgrading-private-github-repositories/141597/1 "2020-02-14T11:12:36Z")

</div>

Hi all again 🙂  
I usually perform upgrades from the admin console insead from the shell. One of the plugins is located in a private Github repo with keys. I committed some changes to the private repo but in upgrades section of the admin console, it shows me “Up to date” with an old hash commit.  
Can the console handle private repos?  
Thank you 🙂

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 14, 2020, 2:17pm UTC](https://meta.discourse.org/t/upgrading-private-github-repositories/141597/2 "2020-02-14T14:17:45Z")

</div>

Should do, yes, so long as you use a token as part of the URL, then it won’t prompt for username and password.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [January 11, 2024, 8:10pm UTC](https://meta.discourse.org/t/upgrading-private-github-repositories/141597/3 "2024-01-11T20:10:38Z")

</div>