DOC: Instruct to run git bisect when triaging a regression report
@rhshadrach (ref #55311)
The issue suggested to include the results of a git bisect when triaging regressions.

As for step 7, it says "what labels and milestones should I add" but has no instructions on adding milestones, the only thing I'm aware of is generally regressions are to be fixed as soon as possible so add to the next patch release, if that is not correct then I'll just rename the section.

Another note is that many steps suggest to edit the original post/title but triage permissions aren't sufficient for that, should I delete those?
>  the only thing I'm aware of is generally regressions are to be fixed as soon as possible so add to the next patch release

Yeah I would say this is generally correct. Any other milestone (major or minor release) are used by some core team members as "issues that would be nice to address by this release", so no need to include that in triage instructions Thanks @Aloqeely 