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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Follow these instructions for contributing new recipes. The Goal headers indicat
72
72
2. Build and test your recipe.
73
73
- The necessary commands to launch your recipe were printed after running `scripts/newRecipe.sh`. Hopefully you copied some of them. If not, you may consult these [instructions on running recipes](https://github.com/JordanMartinez/purescript-cookbook/blob/master/README.md#running-recipes).
74
74
- **Note:** `make` commands must be run from the cookbook's root directory.
75
-
- **Tip:** If you'd like to automatically rebuild recipes after saving changes and your IDE is being uncooperative, you can run `make MyNewRecipe-build-watch` while in the root folder.
75
+
- **Tip:** If you'd like to automatically rebuild recipes after saving changes and your [IDE is being uncooperative](https://github.com/JordanMartinez/purescript-cookbook/issues/230), you can run `make MyNewRecipe-build-watch` while in the root folder.
76
76
1. Update your recipe's `README.md` file by doing the following things:
77
77
1. Write a summary of your recipe on the 3rd line. This is what will appear in the repo's Recipe section's Table of Contents. Don't add newlines unless you're okay with that additional content being omitted from the table.
78
78
1. Update the "Expected Behavior" section to describe in more detail what should occur when users run your recipe.
0 commit comments