So I wanted to update the theme I’m using, as a nice automatic “copy” button had been added for code-blocks. Unfortunately I hadn’t updated my version in a while, and since I had directly changed some files in the theme, the first stumble-block was a few merge conflicts.

And to repeat, since I had directly changed some files in a repository I don’t have commit rights to, I had nowhere to store my changes so they could be available from a different computer either.

To fix all of this I made a fork of the theme and manually added back my changes. Since I now have my own copy of the theme I can commit my changes and have them available wherever I need them. Then it was just a matter of changing the source of the theme from original author to mine, and everything was good.

An added bonus is that I can easily see in my own repo if original author has made any changes on his side, and github also tells me if there are any merge conflicts or not. Hopefully this means it will be easier for me to keep the theme in sync, just as long as I update/check for changes once in a while.

This has been a small blocker for me a little while, that’s why the “silence”. Now to test if everything works as it should when published (there were some changes to how scripts are loaded, and I have strict CSP headers set) and continue my learning process.