version-updates + shield icons make anchors painful

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference#assignees--

What changes are you suggesting?

Omit the version-updates and shield trailers from anchor names.

It seems incredibly unlikely that you would have both a foo and foo[version-updates] or foo[version-updates][shield] anchor in the same page.

Additional information

Compare

• https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference#update-types-groups
  

• https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference#ignore--
  

[Sharra-writes]

@jsoref As a preliminary, talking casually with other people on the team, I'm being told we're not going to prioritize changing this. I will ask if there's an important reason to keep it or if it's something we would let open source contributors change (no one seems to know exactly why it's there), but I just wanted to warn you about the bandwidth capabilities of the team as a whole.

[jsoref]

My guess is that it's part of the core site and not a part that the open source community is allowed to touch. -- I haven't looked. It's a rare case where I'd almost be inclined to ask an agent...

[github-actions]

A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

[github-actions]

A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

[jsoref]

@Sharra-writes

[subatoi]

Hi @jsoref, apologies for the late conclusion here

As Sharra's answer already implied, this isn't something we can guarantee any action or a timeframe for. Since it's not strictly content-related (in the context of this repo and its Issues function), all we can do is pass the feedback along to the relevant team internally.

Sorry this wasn't the answer you were looking for. Thanks, as ever, for your interest in the GitHub docs 🙇

[jsoref]

Frankly, that's about as good of an answer as I could hope to get. Thanks!