# Temas remotos não estão no banco de dados

**URL:** https://meta.discourse.org/t/remote-themes-not-in-database/101619
**Category:** Feature
**Created:** [Novembro 8, 2018, 6:09pm UTC](https://meta.discourse.org/t/remote-themes-not-in-database/101619 "2018-11-08T18:09:55Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![danekhollas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/danekhollas/32/79637_2.png) [@danekhollas](https://meta.discourse.org/u/danekhollas)
#### Post date: [Novembro 8, 2018, 7:23pm UTC](https://meta.discourse.org/t/remote-themes-not-in-database/101619/6 "2018-11-08T19:23:52Z")

</div>

> [@Stephen](#):
>
> An icon indicating where the theme came from (upload/CLI/github) with any URLs in the tooltip would be hugely helpful when digging into this stuff.

> [@codinghorror](#):
>
> Cc @Johani and @sam we need this.

FYI Already discussed here:

> [@Display link to github for remote themes](https://meta.discourse.org/t/display-link-to-github-for-remote-themes/99490):
>
> Hi folks, it would be nice if a remote theme page contained a direct link to the respective Github repo. There is a link “About theme” which typically leads to a topic here on meta (where the link to github can be found) and the License link would typically link to the github repo. However, both of these are useless if you happen to fork a theme and make local modifications. Maybe something like this could work? [image] Alternatively, the link could be below the Check updates button. Also,…

I started working on a PR but got stuck. I can have a second look this weekend, but am happy to pass over.

---

_[View the full topic](https://meta.discourse.org/t/remote-themes-not-in-database/101619)._
