From 4331642a1e8a2f1376106324bd354cae355ffda1 Mon Sep 17 00:00:00 2001 From: TwoSixtyThreeFiftyFour <108928957+TwoSixtyThreeFiftyFour@users.noreply.github.com> Date: Sun, 31 Jul 2022 14:14:11 +0000 Subject: [PATCH] Updates links from old to org repo Updates links from old to org repo --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b26547f..21b9da1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -49,13 +49,13 @@ When reporting guide issues: Please split large sets of changes into multiple PRs. For example, a PR that adds Windows 11 support, removes Windows AME references, and fixes typos can be split into 3 PRs. This makes PRs easier to review prior to merging. -For an example of what *not* to do, see: . This PR contains enough changes to split into multiple smaller and individually-reviewable PRs. +For an example of what *not* to do, see: . This PR contains enough changes to split into multiple smaller and individually-reviewable PRs. ### Updating PRs While a PR is being reviewed, modifications may be made to it by the reviewer prior to merging. If this is the case, a new branch will be created for the PR's review. If you would like to submit a change to a PR that is in the process of being reviewed, *do not update the PR directly*. This will only cause merge conflicts and delay the PR from being merged. Instead, submit your changes to the PR's review branch. -For an example of what *not* to do, see: . Instead of submitting changes to the PR directly, they should have been submitted as changes to the [PR's associated review branch](https://github.com/NobodySpecial256/thgtoa/tree/pr/51). +For an example of what *not* to do, see: . Instead of submitting changes to the PR directly, they should have been submitted as changes to the [PR's associated review branch](https://github.com/NobodySpecial256/thgtoa/tree/pr/51). ---