Resolves #75109

[vidhupv]

New commits include uploading the new screenshot to docs under the name SwiftGithubCreatePRScreenshot.png and also changing the name of the screenshot location in the HowTo Guide for "First Pull Requests"

[AnthonyLatsis]

• Please take the screenshot directly from https://github.com/swiftlang/swift, which is where the doc suggests us to navigate. You could even crop it somewhat like this without the org name that brought about this issue:

  

• The rest of our screenshots are in light mode. Let’s be consistent about that.

• Mind tidying up the commit history and giving this pull request a proper title?

[vidhupv]

@AnthonyLatsis I shall do that. Just a couple of questions:

1. Should I do it exactly the way you sent or should I include the swiftlang/swift portion at the top of the page as well considering how that was in the current screenshot.
2. Should I convert this pull request to draft in order to tidying the commit history?

[AnthonyLatsis]

1. What do you think?
2. No need. The draft state is to indicate that changes are not ready for review. For example, reviews are not requested until you undraft if you start off with a draft PR.

[AnthonyLatsis]

Could you try tidying up your commit history by squashing your commits via an interactive rebase rather than spawning new PRs? Let me know if you need help with that. You will definitely benefit from this skill if you are planning to contribute more. Also, we prefer rebasing on main over merging with main when resolving conflicts — these intermediary merge commits pollute the commit history for no good reason.

[vidhupv]

Hey, I would greatly appreciate any help on that. I am just learning to use the rebase editor on my terminal. I have dropped a few previous redundant commits and am in the process of squashing the valid ones right now.

[AnthonyLatsis]

Hey, I would greatly appreciate any help on that.

Sure, feel free to reach out if you get stuck with anything specific.

[AnthonyLatsis]

Superseded by #75220.