Add triage notes about redistributors

[pradyunsg]

x-ref: #9677

[stefanor]

👍 for the Debian and Ubuntu wording.

[DiddiLeija]

@pradyunsg, the text looks like Markdown, but it should be ReStructuredText 😄. Excluding that, I give this PR a +1.

[uranusjr]

The Markdown is in a code block that’s supposed to be copied into a GitHub issue. So the syntax is correct here, I think.

[uranusjr]

The rst-backticks check needs be made smarter to ignore single ticks in a code block.

[DiddiLeija]

The Markdown is in a code block that’s supposed to be copied into a GitHub issue. So the syntax is correct here, I think.

If so, we can merge this now :)

The rst-backticks check needs be made smarter to ignore single ticks in a code block.

I'll send an issue to pre-commit/pygrep-hooks.

[DiddiLeija]

I'll send an issue to pre-commit/pygrep-hooks.

See pre-commit/pygrep-hooks#95. Thinking a bit more about this, can development/issue-triage.rst become a Markdown file, such as development/issue-triage.md? This should resolve the CI checks for now.

[uranusjr]

Or we can just use double backticks in Markdown 😉 Markdown is permissive regarding inline code, it works as long as the opening and ending numbers match.

[DiddiLeija]

Or we can just use double backticks in Markdown 😉 Markdown is permissive regarding inline code, it works as long as the opening and ending numbers match.

@pradyunsg Can we try this to avoid CI failures in future PRs?

[pradyunsg]

Thinking a bit more about this, can development/issue-triage.rst become a Markdown file, such as development/issue-triage.md?

I've done this. I wanna move the entire documentation to Markdown wherever possible anyway. :)

[pradyunsg]

Merging this, since I imagine this is fairly non-controversial. If there's concerns on this, holler here! :)