EditorConfig support for GitHub
GitHub EditorConfig Extension
It looks for .editorconfig files in the repository the current file belongs to, and applies found settings to code viewer and editor. Branch is always taken into account.
You can also set default editorconfig that will be used for repos without custom one. By default, it fixes tab size to 4 spaces per tab for all files but Ruby (2 spaces per tab).
Source Manifest.json
How to download and manually install GitHub EditorConfig extension for Chrome
Looking for a way to install GitHub EditorConfig extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.
However, you may need to install GitHub EditorConfig extensions manually, this article outlines two simple methods to effortlessly install GitHub EditorConfig extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.
Method 1: Download GitHub EditorConfig extension and manually install through Drag &Drop
If you ever need to manually install a GitHub EditorConfig extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.
Step 1: Download the GitHub EditorConfig Extension by clicking the "Download CRX" button on the website.
Look for the GitHub EditorConfig extension you wish to install. Go to the website and download the GitHub EditorConfig extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for GitHub EditorConfig extension that contains all the data.
Step 2: Extract &Arrange Files
Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.
Step 3: Go to the Chrome Extensions Page
Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.
Step 4: Drag and Drop the Extension
Now, go to the folder where you extracted the GitHub EditorConfig extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.
Step 5: Complete the Installation
Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.
Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.
Method 2: Download GitHub EditorConfig extension for Chrome and install in Developer Mode
This is another method to install GitHub EditorConfig extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.
Step 1: Download the GitHub EditorConfig extension file
Select and download the GitHub EditorConfig extension by clicking the 'Download CRX' button on the website.
Step 2: Extract the downloaded contents
Convert the file to a ZIP file if it is in CRX format then extract the GitHub EditorConfig extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your GitHub EditorConfig extension running.
Step 3: Open Chrome Extension Setting Page
In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.
Step 4: Enable Developer Mode
After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.
Step 5: Load the Unpacked Extension
Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."
Step 6: Select the Extension Folder
Once the pop-up opens upon clicking Load unpacked, select the GitHub EditorConfig extension directory and click on the "Select Folder "button.
Step 7: Confirm and Install
After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.
Conclusion
Here we've made a step-by-step guide on How to manually install GitHub EditorConfig extension in 2 ways. We hope this guide proves helpful.
Similar Extensions
Twitter for GitHub 326 5 ★ 19.72KiB
github.expandinizr 326 29 ★ 68.69KiB
Github diff helper 326 3 ★ 137KiB
HackerNotes Plugin 326 3 ★ 17.62KiB
github-find 326 1 ★ 40.7KiB
Contributors on Github 326 5 ★ 15.6KiB
Diff Navigator for GitHub 326 3 ★ 43.72KiB

Nodei.co: npm badges for GitHub 326 6 ★ 24.33KiB
GitHub Enhancement Suite 326 1 ★ 56.24KiB
GitHub submodule links 326 2 ★ 17.49KiB
OctoLinker 326 110 ★ 184KiB
Git flow (for Github) 326 1 ★ 218KiB
Codebox Button for GitHub 326 2 ★ 11.74KiB
Github Package.json Enhancer 326 0 ★ 18.89KiB
Github Super Search 326 0 ★ 46.74KiB
Github Toc 326 7 ★ 704KiB
Table of Contents for GitHub 326 4 ★ 11.44KiB

Markdown Menu for GitHub 326 9 ★ 5.8KiB
github npm stats 326 4 ★ 65.86KiB
Pretty Pull Requests (Github) 326 21 ★ 412KiB
Helper for GitHub notifications in Gmail 326 7 ★ 19.64KiB
Package Hub 326 2 ★ 28.3KiB
Github Node.js require() navigator 326 8 ★ 509KiB
GitHub Issue Link Status 326 12 ★ 629KiB
User reviews
Lavender Shannon (ID: 000000a65c25df22) Voted 5 ★ - Updated 06/17/2018
Aaron Jensen (ID: 0000005564487d67) Voted 5 ★ - Updated 11/09/2014