Add a link to report a general issue

[0xPoe]

close #3129

[rust-highfive]

r? @smarnach

(rust-highfive has picked a reviewer for you, use r? to override)

[0xPoe]

I'm not sure we should force a line break?

[JohnTitor]

The change itself looks good, though I'm going to defer the final review to another reviewer as I'm not sure if we need a style change.

[0xPoe]

PC:

mobile:

[0xPoe]

r? @jtgeibel

Could you please take a look? Thanks!

[0xPoe]

@Turbo87

Could you please take a look? Thanks!

[Turbo87]

probably not the final state of the footer, but I guess this is a good intermediate step :)

[Turbo87]

@bors r+

[bors]

📌 Commit ad0fba5 has been approved by Turbo87

[bors]

⌛ Testing commit ad0fba5 with merge 0435e20...

[bors]

☀️ Test successful - checks-actions
Approved by: Turbo87
Pushing 0435e20 to master...

[epage]

As a user, "report an issue" sounds definitive, that I know there is an issue. I don't remember what issue led to #3129 but I had written "I was trying to get support with a potential problem with crates.io". The new link would not have helped me in this case. I probably would still click "send an email" because (1) it sounds closest to a means of support and (2) there is no clarification on when emailing should be used.

[0xPoe]

As a user, "report an issue" sounds definitive, that I know there is an issue. I don't remember what issue led to #3129 but I had written "I was trying to get support with a potential problem with crates.io". The new link would not have helped me in this case. I probably would still click "send an email" because (1) it sounds closest to a means of support and (2) there is no clarification on when emailing should be used.

The link I added here is report a general issue , maybe we do need a link that explains how to use them. This is not the final footer state, maybe we can consider it in a future design?

Also, I added it just thinking we could jump to here via a direct link. It's also what you mentioned in the possible alternative solutions.