Fixed troubleshooting header id and added pre-commit installation troubleshooting

[tbhaxor]

Description

This pull request contains the two this

1. Fix for the id of the "LightDM" troubleshooting. #id1
2. Add instructions to fix the pre-commit installation here

Motivation and Context

How Has This Been Tested?

Locally on Linux using docs build command

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• If my change requires a change to the documentation, I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
• I have added tests to cover my changes, and all the new and existing tests pass.

[cornfeedhobo]

@davidpfarrell LGTM, but could you please give this a look over?

[davidpfarrell]

Greetings !

I'm looking at the reStructuredText Markup Specification
page and can't find reference to this <#..> usage - Can you point me to it? And/or maybe other online examples of this usage?

[davidpfarrell]

Why is it #id3 instead of #id2 ?

[tbhaxor]

This is called id attribute scroll/focus. I checked that in restructured text, it is setting the id attribute to #id1. Which is wrong in the current https://bash-it.readthedocs.io/en/latest/troubleshooting/im-stuck-in-the-lightdm-login-screen-after-setting-up-bash-it redirected to 404 whereas https://bash-it.readthedocs.io/en/latest/troubleshooting/#id1 takes to the correct heading on the troubleshooting page.

[tbhaxor]

These ids' are of the section headers generated by the rst. Even I am wondering why it didn't slugify the header text instead.

[tbhaxor]

Greetings !

I'm looking at the reStructuredText Markup Specification page and can't find reference to this <#..> usage - Can you point me to it? And/or maybe other online examples of this usage?

`Content <link>`_ is basically a syntax in rst which gets converted to [Content](link) in markdown or <a href="link">Content</a> in html. You can have any type of link

• Absolute → https://example.com/
• Relative → /my-page
• Hash → #element-id

[tbhaxor]

Timeout