build: include comments and code snippets in created issues

[Planeshifter]

Description

What is the purpose of this pull request?

This pull request:

• updates formatting for commit comment issues to both include the comment bodies and a code preview, making code review easier for PRs addressing these issues. See below for how the proposed new formatting will look like.

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves [RFC]: Include code preview and full original comments in commit comment issues metr-issue-tracker#7

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

New issue body example:

===

This commit has 2 comment(s) from core contributors that require attention.

Commit: e05da283a2493c635c06ab0f19e4aefbcc9e2540

Comments:

• e05da28#r152671098

  174: @stdlib-bot should be // returns 3.0

  stdlib/lib/node_modules/@stdlib/stats/base/dists/binomial/stdev/README.md

  Lines 171 to 177 in e05da28

  	```c
  	double out = stdlib_base_dists_binomial_stdev( 100, 0.1 );
  	// returns 3
  	```
  	The function accepts the following arguments:

• e05da28#r152671105

  184: @stdlib-bot Missing triple backticks to close the code block.

  stdlib/lib/node_modules/@stdlib/stats/base/dists/binomial/stdev/README.md

  Lines 181 to 187 in e05da28

  	```c
  	double stdlib_base_dists_binomial_stdev( const int32_t n, const double p );
  	</section>
  	<!-- /.usage -->

Interested in helping improve the project? If you are, the comment linked to above has 2 comment(s) from core contributors that could use your attention.

What do you need to do?

1. Open the above linked comments mentioning @stdlib-bot.
2. Review the suggested changes or follow-up tasks (e.g., formatting improvements, small refactorings, or clean-up).
3. If you are a first-time contributor, follow the contributing and development guides to setup your local environment for contributing to stdlib. If you are already a seasoned stdlib contributor, create a new branch on your local fork for making the changes.
4. Make all the desired changes and commit those changes to a local branch.
5. Push the changes to GitHub and open a new pull request against the develop branch of the main stdlib development repository.

Once you've opened a pull request, a stdlib maintainer will review your work and suggest any follow-up changes.

And that's it!

Thank you for your help in reducing the project backlog and in improving the quality of stdlib. 🙌

---

Notes

• For older commits, there is a chance that comments will have been already been addressed due to other refactorings. If you find that to be true, don't worry! Just move on to addressing the next comment, and, when opening your pull request and describing your proposed changes, be sure to link to the comment and mention that it has been addressed. This will help reviewers when reviewing your code!

---

This issue was created automatically to address commit comments tagging @stdlib-bot.

===

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[kgryte]

Looks great! Can we prefix the line number in the list element with Line: ?

[kgryte]

LGTM! Thanks!