Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Affected page Your code Typical user code: Expected behavior We've had an uptick of people blindly copying the help video from this challenge without reading the instructions: This leads to campers failing the requirement (This is generally a problem with the help videos, unfortunately - copying with zero understanding.) Does this video link need to be updated or removed? Screenshots If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. System (please complete the following information): Device: [e.g. iPhone6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4] Browser: [e.g. chrome, safari] Version: [e.g. 22] Additional context Add any other context about the problem here.
let's remove it, it's already that direction with other videos, once there is a discrepancy, the challenge win and the video is removed
Seeing as this is an easy fix (I assume we just remove the URL) I will open this up to first-timers. If anyone disagrees feel free to remove the label.
Thanks for making this a first timers only. The only additional step I would be recommending is using as an example to add clear instructions for first timers. I am going to go ahead and take care of that here. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: Edit this file and remove the line containing . Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull-requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Thanks for the help. I have the template to a saved reply. Hopefully, I will remember to use it. Also, I have a stupid question. How do you best "quote" the code and line numbers of a .md file? Do you just use the blame view or look at a commit/PR? I don't understand the commit link you have in your quote. It looks to be for something else?
Oh - I just use the code view for a markdown file and then grab the permalink. <details<summaryDetails</summaryOpen file in code-view: It's the icon on the left at the top right of the file. Looks like this: ! Getting the permalink by selecting the line (host shift for more lines): ! </details
Right, but you can only get to the code view from inside a commit, right? I mean I do not see the source view for .md files when just looking at the file. Anyway, I will figure it out sorry to bother you with this I know you are a busy man.
Yes, that is correct. I browse the repo with top commit at the time of making a comment. But again, you do not have to spell out every little detail for the first-timers, it's just a "the more the better" type thing.

Discussion:
id: bad87fee1348bd9aede08817 title: Nest an Anchor Element within a Paragraph challengeType: 0 <del> videoUrl: 'https://scrimba.com/p/pVMPUv/cb6k8Cb' </del> forumTopicId: 18244 dashedName: nest-an-anchor-element-within-a-paragraph ---