Update: Browsing through the discussions, looks like this is a known “issue”: https://help.micro.blog/t/pushing-theme-updates/1067.
Would be great if micro.blog would pick up the changes automatically from GitHub, but refresh/reload button would work just as fine too. Maybe at some point! 
Chiming in for this topic too 
I got confused about the difference of themes vs. plug-ins today too.
The process I had in mind:
- Make a fork of existing theme (Marfa)
- Clone that repo to my local machine
- Enable this forked theme via Design → Edit custom themes
- Make changes to the theme repo on my local machine and push changes
- See how my micro.blog theme picks up those changes…
That’s how I pictured the process, but I don’t think it goes like that, does it? I think micro.blog doesn’t pick up those repo changes automatically? Or did I miss something?
I guess what I’m asking: What is the ideal process of forking an existing micro.blog theme, making it mine and keeping it up to date in micro.blog (preferably via making changes to the theme via in a GitHub repo)?
Thanks!