From 024482d4e8f01e63bac5acd01f64ce5f15c73cc2 Mon Sep 17 00:00:00 2001 From: Jordan Bancino Date: Sat, 9 Sep 2023 16:57:52 -0400 Subject: [PATCH] Put the finishing touches on `CONTRIBUTING.md`. --- docs/CONTRIBUTING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index 23ed244..0faf4ac 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -16,7 +16,7 @@ page. Donations of any size are greatly appreciated. An important way to get involved is to just report issues you find with Telodendria during experimentation or normal use. To report an issue, go to [Issues](/Telodendria/telodendria/issues) → -[New Issue](/Telodendria/telodendria/issues/new) and follow the +[New Issue](/Telodendria/telodendria/issues/new/choose) and follow the instructions. > **Note:** GitHub issues are not accepted. Issues may only be @@ -106,7 +106,8 @@ as many as were in `td`. Telodendria follows the standard pull request procedures. Once you have made your changes, committed them, and pushed to your fork, you should be able to open a pull request on the main repository. When you do, you -will be prompted to write a description +will be prompted to write a description. Be sure to include the +related issue that you are closing in your description. ### Code Style @@ -159,3 +160,4 @@ comments to the appropriate header. If your pull request does not also include proper documentation, it will likely be rejected. +