This was 50% started in the last devlog but I decided to only write about it here.

I ran into a major issue with the github REST API - rate limits. If your project had 200+ files, then it would run into the rate limit for sure. And while I could’ve let this limit stay and make it easier on myself, I decided that I didn’t want to live within this limit, and it was time to look for a new git solution.

The solution: isomoprhic-git. Its a library that gives FULL git compatibility and features but its written completely in javascript. The only bummer was that it was a git clone, meaning it created a .git folder and operated out of that. I really dont like the idea of having a .git folder shadow a twig user, because then what is the point of someone using my version control, right?

so heres how github pushing/pulling works with twig and isomorphic git.

when you use the github push command, twig creates a folder called “twig-engine” within the “.twig” folder and that twig-engine folder is basically a “.git” folder renamed. Then, twig does its needed treeWrite operations in that twig engine folder, pushes it to github, and then deletes the twig engine folder. Basically, it is never seen by the user and only appears when needed.