Enhance PR/Issue templates readability

[kyu08]

PR Description

• I updated PR/Issue templates to enhance their readability.
• I hope this change can reduce the maintainer's burden to read PR/Issue, even a little bit.
• Of course, it is most important how the maintainers feel about this change, so if you don't need this, I have no objection to closing this PR.
• By the way, I use the template I changed for this PR. What do you think?

e.g. This is how PR template changed.

Before
After

Please check if the PR fulfills these requirements

• Cheatsheets are up-to-date (run go generate ./...)
• Code has been formatted (see here)
• Tests have been added/updated (see [here](https://github.com/jesseduffield/lazygit/blob/master/pkg/integration/README.md) for the integration test guide)
• Text is internationalised (see here)
• If a new UserConfig entry was added, make sure it can be hot-reloaded (see [here](https://github.com/jesseduffield/lazygit/blob/master/docs/dev/Codebase_Guide.md#using-userconfig))
• Docs have been updated if necessary
• You've read through your own file changes for silly mistakes etc

[kyu08]

This part is rendered like:

[kyu08]

You can enforce using template upon the authors if you put .github/ISSUE_TEMPLATE/config.yml and set blank_issues_enabled: false.

ref: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

If you need it, I can add it.

[kyu08]

I added periods for consistency with other templates.

[stefanhaller]

Nice, looks good. My only question is whether we should use H3 instead of H2 for the section headers, both in the issue template and the PR template. For my taste, the H2 headers look a little bit too big.

[kyu08]

Thanks for the feedback!

This is why I prefer starting from h2.

• Semantically, I think it would be more natural to start with h2.
• It would also be more convenient for authors when they want to create deeper nesting if the template starts with h2 (if it started with h3, they would need to use larger heading numbers).
• From h3 onwards, there are no underlines, which may make it a bit harder to read(though this is a matter of preference)
  

But this is mainly a matter of preference and appearance, and it's not a strong opinion where I absolutely insist on starting with h2.
So I can follow your final decision and I can discuss more about this if needed.

[stefanhaller]

• It would also be more convenient for authors when they want to create deeper nesting if the template starts with h2 (if it started with h3, they would need to use larger heading numbers).

There are still three more nesting levels available after h3, so I don't see this as a problem. I din't think anyone will create this many additional levels.

• From h3 onwards, there are no underlines, which may make it a bit harder to read

That's actually one of the reasons why I prefer h3, I think the underlines make too much separation.

But I agree that it's mainly a matter of taste, so it's probably not worth arguing about it much longer.

[kyu08]

That's actually one of the reasons why I prefer h3, I think the underlines make too much separation.
But I agree that it's mainly a matter of taste, so it's probably not worth arguing about it much longer.

I see. 👍
I replaced h2 with h3. eb922f8
Please review it when you have some time.

[stefanhaller]

Nice, thanks.