@EcutDavid we're going to release v0.12 soon and it would probably be a good idea to put this there (since v0.12 deals with theme changes). Do you mind submitting this PR to the v0.12 branch instead?

@shaurya947 Ok :)

@EcutDavid we merged v0.12 into master so I'll re-open this. Could you please rebase so we can go ahead and merge this?

Hi rebase done, and I pull the changes to my repo, what's the next???
It's my first time rebase, a little confuse :(

@EcutDavid here's a good overview of what rebasing does (from link):

[Rebasing] works by going to the common ancestor of the two branches (the one you’re on and the one you’re rebasing onto), getting the diff introduced by each commit of the branch you’re on, saving those diffs to temporary files, resetting the current branch to the same commit as the branch you are rebasing onto, and finally applying each change in turn.

So once you have rebased, push your local branch (instead of pull, do a force push if needed with the -f flag) so that your remote branch is updated. Let me know if you need more help!

@shaurya947 Thank you very much, I did it :)

@EcutDavid something seems a little off. There are a few commits in the PR that are already in master. Do you mind taking a look again? You got any suggestions @oliviertassinari ?

Ok, I will take a look again In the midday :)
Live in china, it's 8:30 AM now, and have to work~
My company not allow deliver code @ github during working time.

Do you want me to rebase and open a PR with your commits?
I think that we need to fix the theme section of the doc before releasing.

Sorry, I made some mistake,

OK it works now~

Cool stuff, thanks @EcutDavid!