You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You may have noticed some error about providing a form key. This is because we use [Formspree](https://formspree.io/) to handle our contact form. To get around this, you can:
100
96
@@ -104,30 +100,31 @@ You may have also noticed a second error about missing required parameters: site
104
100
105
101
- Use your own [reCAPTCHA](https://www.google.com/recaptcha/about/) account and set the `RECAPTCHA_SITE_KEY` environment variable to your keys. (refer to the .env.example file for guidance on where to put your recaptcha site key).
106
102
107
-
108
103
Both of these changes will require you to create a `.env` file in the root directory of the project. You can copy the contents of the `.env.example` file and paste them into the `.env` file. Then, you can add your keys to the appropriate variables.
109
104
110
-
***
105
+
---
106
+
111
107
<br>
112
108
113
109
3. Make changes to the codebase
114
110
115
111
- Open this directory in your favorite text editor / IDE, and see your changes live by visiting `localhost:3000` from your browser
116
112
- Pro Tip: Explore scripts within `package.json` for more build options
113
+
- Pro Tip: Use [Prettier](https://prettier.io/) to format your code before committing by running `npm run prettier:check` and `npm run prettier:format` to check and fix formatting issues
117
114
118
-
1. Add changes made to the repo addressing an issue
115
+
4. Add changes made to the repo addressing an issue
119
116
120
117
```bash
121
118
git add [file_name]
122
119
```
123
120
124
-
2. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
121
+
5. Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see [how to link a commit message to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
125
122
126
123
```bash
127
124
git commit -m "brief description of changes [Fixes #1234]"
0 commit comments