Problem
The release QA Slack notification (#35825 / merged PR #35815) renders each bucket count as a link to the workflow run summary with a per-bucket fragment, e.g. …/actions/runs/<id>#qa-missing. Clicking it lands at the top of the run page instead of the Missing QA section.
Example: https://github.com/dotCMS/core/actions/runs/26459945291#qa-missing
Root cause
GitHub's markdown sanitizer rewrites anchor ids in the job summary with a user-content- prefix (a DOM-clobbering safeguard applied to all rendered markdown). The summary declares <a id="qa-missing"> but the rendered element is id="user-content-qa-missing", so the bare #qa-missing fragment matches nothing and the browser stays at the top.
This is documented GitHub behavior — the working fragment for a custom anchor in a job summary is #user-content-<id>.
Fix
Point the Slack count links at #user-content-<anchor>. The markdown <a id="..."> markers stay as-is (GitHub adds the prefix on render).
PR: #35842
Problem
The release QA Slack notification (#35825 / merged PR #35815) renders each bucket count as a link to the workflow run summary with a per-bucket fragment, e.g.
…/actions/runs/<id>#qa-missing. Clicking it lands at the top of the run page instead of the Missing QA section.Example: https://github.com/dotCMS/core/actions/runs/26459945291#qa-missing
Root cause
GitHub's markdown sanitizer rewrites anchor
ids in the job summary with auser-content-prefix (a DOM-clobbering safeguard applied to all rendered markdown). The summary declares<a id="qa-missing">but the rendered element isid="user-content-qa-missing", so the bare#qa-missingfragment matches nothing and the browser stays at the top.This is documented GitHub behavior — the working fragment for a custom anchor in a job summary is
#user-content-<id>.Fix
Point the Slack count links at
#user-content-<anchor>. The markdown<a id="...">markers stay as-is (GitHub adds the prefix on render).PR: #35842