# Should I keep my theme on GitHub or not?

**URL:** https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071
**Category:** Development
**Created:** [August 6, 2019, 11:58pm UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071 "2019-08-06T23:58:39Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![bifterx](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bifterx](https://meta.discourse.org/u/bifterx)
#### Post date: [August 6, 2019, 11:58pm UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/1 "2019-08-06T23:58:39Z")

</div>

Sorry if this sounds a bit naive. We have done a fair bit of styling, simple stuff but a fair bit to our Discourse theme with custom CSS tweaks etc. Its a hosted plan, every time I make changes to the CSS in the UI it gives me a warning in regards to updates and overwriting.

Is it best practice to set up a GitHub repo and host all the theme files and theme components there to avoid this issue?

cheers  
rob

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 7, 2019, 12:03am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/2 "2019-08-07T00:03:20Z")

</div>

Absolutely, it is best practice to keep any sizeable theme on a Git repo. It makes tracking changes easier, using theme creator CLI the workflows are delightful so its even easier to hack on.

---

<div class="post-metadata">

### Author: ![bifterx](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bifterx](https://meta.discourse.org/u/bifterx)
#### Post date: [August 7, 2019, 12:04am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/3 "2019-08-07T00:04:35Z")

</div>

thank-you sam, decision made.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 7, 2019, 2:27am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/4 "2019-08-07T02:27:04Z")

</div>

> [@sam](#):
>
> using theme creator CLI the workflows are delightful

I’ve missed that. The cli will, what, see that a change has been pushed to github and reload it? I’ve only seen it push local files to discourse. I just reread the announcement and don’t see anything there about github.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 7, 2019, 2:31am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/5 "2019-08-07T02:31:41Z")

</div>

You would check out GitHub locally 🙂 that way you do all your edits locally, eventually once done you would push it to GitHub.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 7, 2019, 2:37am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/6 "2019-08-07T02:37:32Z")

</div>

Ah, so you’d do development on a staging site with the cli, push to github, and production pulls the update from github?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 7, 2019, 2:39am UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/7 "2019-08-07T02:39:01Z")

</div>

You can dev on production just fine, you would create a temporary component / theme and just give it a diff name. Something like that.

But yeah staging+dev workflow can work a bit more cleanly.

---

<div class="post-metadata">

### Author: ![Joshua\_Kogan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/joshua_kogan/32/127595_2.png) [@Joshua\_Kogan](https://meta.discourse.org/u/Joshua_Kogan)
#### Post date: [August 7, 2019, 2:17pm UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/8 "2019-08-07T14:17:51Z")

</div>

I’m really interested in seeing people’s themes – have a live link?

---

<div class="post-metadata">

### Author: ![bifterx](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bifterx](https://meta.discourse.org/u/bifterx)
#### Post date: [August 7, 2019, 2:47pm UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/9 "2019-08-07T14:47:50Z")

</div>

we are not quite live yet. ill post couple of screens

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [August 9, 2019, 8:58pm UTC](https://meta.discourse.org/t/should-i-keep-my-theme-on-github-or-not/125071/10 "2019-08-09T20:58:45Z")

</div>

Oh, wow! I just used it for the first time in a while (after I couldn’t make it work for 2 days because I forgot that you have to use a use API key and thought that there was a different problem, but ~~I digress~~ I just edited the topic to tell people that) and WOW it’s crazy-great now.
