From 402b88588395bc0cf04d683472a9a103f4589847 Mon Sep 17 00:00:00 2001 From: "Brady Stroud [SSW]" Date: Sun, 6 Oct 2024 01:24:03 +0930 Subject: [PATCH] =?UTF-8?q?XS=E2=9C=94=20=E2=97=BE=20Pr=20suggestions=20-?= =?UTF-8?q?=20add=20video=20(#9350)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pr suggestions - add video --- rules/pr-suggest-changes/rule.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/rules/pr-suggest-changes/rule.md b/rules/pr-suggest-changes/rule.md index bae49da30f6..602fdc21ac7 100644 --- a/rules/pr-suggest-changes/rule.md +++ b/rules/pr-suggest-changes/rule.md @@ -20,6 +20,9 @@ guid: 8b529efe-d500-42b8-9632-7de23506546a Normally, the best way to provide feedback on content changes is to use the [change X to Y format](/change-from-x-to-y). When it comes to reviewing Pull Requests (PRs) in GitHub, this is not the case - it's inefficient for the PR owner. They have to manually interpret each suggested change, implement them in the code, and then commit the changes, which can be time-consuming. +`youtube: https://youtu.be/xSSz3vPDi4g` +**Video: Pull Request Suggestions | Brady Stroud | SSW Rules (4 min)** + ::: bad ![Figure: Bad example - GitHub - Using change X to Y format (need to copy+paste changes)](bad-pr-suggest-changes.png) :::