Sync the site to master branch (and come back to source).

Build site with the production JEKYLL_ENV.

(Assume we are done writing in source branch) Commit and push all changes in source branch.

Create a shell script with all the git commandsįirst we can create a shell script update.sh in the workspace root, and add executable rights to it chmod +x update.sh. If we make sure everything is good locally by doing bundle exec jekyll serve, we can deploy the site by the following. Click 'More info', then 'Run anyway' to continue. On Windows 8, a warning from SmartScreen may appear. This will download binary content for the engine, as well as installing prerequisites and setting up Unreal file associations.

Caveat: this post assumes that our readers are as lazy as myself and do not want to do repetitive things by hand.Īfter the first time done working building the site and syncing the changes to the master, we can streamline this workflow in VSCode by pressing a single key combo…using a task hack. Open your source folder in Explorer and run Setup.bat.Electron is generally known for its slow start up times.

Here I will share how to use VSCode to simplify the workflow, by using VSCode task to execute a customized shell script, which does commit/push and a few other things. VS Code is built with a framework called Electron (developed by Github). switch to source -> commit the changes and push -> build the site -> switch to master -> commit the changes in _site and push -> switch back to source.In a previous post, we covered how to use a custom plugin in Jekyll and deploy our site on GitHub using the source and master branches trick: Set up a VSCode task to execute the shell script.Create a shell script with all the git commands.Shortcut to git commit and push in Visual Studio Code

Visual studio code git first time