

If you pull down new changes or make a change to the extension's files locally, you'll need to hit the "refresh" icon in chrome://extensions/ in order to run the new functionality.
/01_Inspect_Element_Chrome-756549-14d8f0f1d8fe4f8a8996c9650875f833.jpg)
Click "Load unpacked" button and navivigate to the folder you downloaded from GitHub Visit chrome://extensions/ and turn on "Developer mode"ģ.

You will still have to manually "refresh" the extension to see the changes, explained later.Ģ. If you clone or fork the repo, you'll only have to git pull every time you want changes. Use whichever technique fits your workflow and comfort level. Use either technique to get the folder onto your local machine. Here are the three steps to make it happen. Installing Chrome extensions manually from GitHub is a great way to pass around extensions if they are a work-in-progress or otherwise don't need to be in the Chrome store.
