Skip to content

Commit

Permalink
add code spell checker 4101 (#5751)
Browse files Browse the repository at this point in the history
  • Loading branch information
jackyuan1 authored Oct 23, 2023
1 parent 08dda1c commit 84faa2a
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ The following is a set of guidelines for contributing to the website repository,
- [**1.6 Dev setup (6): Build and serve the website locally**](#16-dev-setup-6-build-and-serve-the-website-locally)
- [**1.6.a Starting Docker**](#16a-starting-docker)
- [**1.6.b Stopping Docker**](#16b-stopping-docker)
- [**1.7 Dev setup (7): Install local codebase spell checker**](#17-dev-setup-7-install-local-codebase-spell-checker)
- [**Part 2: How the Website team works with GitHub issues**](#part-2-how-the-website-team-works-with-github-issues)
- [**2.1 Hack for LA Contributor expectations**](#21-hack-for-la-contributor-expectations)
- [**2.2 How Hack for LA organizes issues**](#22-how-hack-for-la-organizes-issues)
Expand Down Expand Up @@ -302,6 +303,15 @@ docker-compose up

<sub>[Back to Table of Contents](#table-of-contents)</sub>

### **1.7 Dev setup (7): Install local codebase spell checker**

You must use VS Code as your local text editor to install the VS Code extension for spell checking your codebase, Code Spell Checker.

The recommended installation method is to install Code Spell Checker directly from the VS Code text editor, and those instructions can be found [here](https://code.visualstudio.com/learn/get-started/extensions). The extension can also be installed via the VS Code Marketplace website [here](https://marketplace.visualstudio.com/items?itemName=streetsidesoftware.code-spell-checker). <strong><em>Feel free to reach out in the [Hack for LA Slack channel](https://hackforla.slack.com/messages/hfla-site/) if you have trouble installing the extension in VS Code.</em></strong>

<sub>[Back to Table of Contents](#table-of-contents)</sub>


***

## **Part 2: How the Website team works with GitHub issues**
Expand Down

0 comments on commit 84faa2a

Please sign in to comment.