DOC: Instruct to run git bisect when triaging a regression report #58813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@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?