Uses RST substitution to put badges in 1 line

[shenxianpeng]

Summary of changes

It might be some update to Github's RST renderer caused badges to display in multiple lines. uses RST substitution to put badges in 1 line.

Before the change

After the change

Pull Request Checklist

• Changes have tests
• News fragment added in newsfragments/.
  (See documentation for details)

[abravalheri]

Thank you very much @shenxianpeng! That was a good catch, I haven't noticed this before your PR.

I think that is a fine change, but I wonder if the best approach would not be to notify GitHub about this regression? (The rationale is that with this change we fix setuptools, but there is a lot of other repositories out there with the same setup; so if GitHub fixes it at the source, everyone benefits).

Should we notify GitHub first and then see their feedback before merging the change?

UPDATE: github/markup#1801

[shenxianpeng]

That would be best if GitHub could address this issue.

[shenxianpeng]

I see that there are nearly no replies from the maintainer under https://github.com/github/markup/issues.
Perhaps reposting github/markup#1801 to the GitHub community discussions would get it more widespread attention.
I see other questions about RST, such as 113792 (another recent regression), but not this one.

[abravalheri]

Thanks @shenxianpeng, I found an open discussion on the topic and reported the problem description there: https://github.com/orgs/community/discussions/114690

[webknjaz]

It might be some update to Github's RST renderer caused badges to display in multiple lines

Yes, I noticed this in many other of my projects. It also looks like they've broken rendering of other things and the overall support of RST on GitHub has always been quite limited.
So I think this is a good change for now but in the future it might make sense to migrate to MyST and regular Markdown...

[abravalheri]

Thank you @shenxianpeng, let's merge it for now... I don't know how long the discussion on the github site will take.

Also the behaviour seems to be an intended change in docutils (¿ possibly ?) as per github/markup#1801 (comment)