Documentation: Change example WSL file path

[Lampe2020]

Because it's possible to have more than one distro in WSL the path to files inside that distro needs to include the distro name

[BuggieBot]

Hello!

One or more of the commit messages in this PR do not match the SerenityOS code submission policy, please check the lint_commits CI job for more details on which commits were flagged and why. Please do not close this PR and open another, instead modify your commit message(s) with git commit --amend and force push those changes to update this PR.

[Lampe2020]

I've shortened the line by breaking it shorter than the other lines, why is it still too long?
Oh, and sorry for closing and re-opening the PR, that's a one-time mistake I promise I'll never make again...

[Lampe2020]

Now all the lines I've changed are sub-72 characters long even though some other lines are 118 characters and longer.

[Hendiadyoin1]

The bot meant your commit message

Use git rebase or git commit --amend to change it

[ADKaster]

@Stehlampe2020 On this project we rebase PR commits directly onto the master branch, rather than squash merging. So, your PR now has two commits, and the first one has a line length that's too long in the commit description. The commit linter error is not about the actual files, but about your commit.

Have a look at this youtube video and ask around in discord in the #development channel if you are having trouble figuring out the git-fu. https://youtu.be/ElRzTuYln0M

Your second commit should actually be dropped from the PR, as it's fixing the wrong thing :)

[Lampe2020]

@Stehlampe2020 On this project we rebase PR commits directly onto the master branch, rather than squash merging. So, your PR now has two commits, and the first one has a line length that's too long in the commit description. The commit linter error is not about the actual files, but about your commit.

Have a look at this youtube video and ask around in discord in the #development channel if you are having trouble figuring out the git-fu. https://youtu.be/ElRzTuYln0M

Your second commit should actually be dropped from the PR, as it's fixing the wrong thing :)

Thanks so much, now I understand the problem. I have pushed another change to my PR so the file is in a good shape again and the description should match the criteria.

[Lampe2020]

I have no idea why the test is still complaining.
I'll go to bed now (I'm pretty tired) and look into it again the next afternoon/evening (in Sweden).

[Lampe2020]

@kleinesfilmroellchen How can I correct the PR with the GitHub.com web interface? Because I somehow cannot get the commandline git to do more witout failing than downloading a repo ...

[kleinesfilmroellchen]

@Stehlampe2020 Please ask more specific git questions on Discord.

[stale[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!

[stale[bot]]

This pull request has been closed because it has not had recent activity. Feel free to re-open if you wish to still contribute these changes. Thank you for your contributions!