Mention in the issues is not working

[fr4nc1sc0-r4m0n]

When creating an issue in some cases (autodoc for instance https://github.com/elastic/oblt-framework/issues/3260) the mention to the @elastic/observablt-ci team is not working fine.

[github-actions]

1 related issue

• [autodoc] Document distribution config contract and complete workflow docs index #91 — it documents prior handling in this repo where team assignment support was uncertain and a team mention was used as a fallback, which may help explain why this issue reproduces in autodoc-generated reports.

---

What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

tl;dr: the most likely root cause is that autodoc issue bodies are created through a safe-output path that neutralizes body @mentions (backticks them), so a body mention to @elastic/observablt-ci will not notify reliably.

Recommendation

Switch team notification from “mention in issue body” to a guaranteed post-create issue comment containing a plain-text mention, and document that body mentions are not a valid notification channel for this path.

Findings

1. In this repo, autodoc currently requires a body mention via prompt text:

.github/workflows/gh-aw-autodoc.yml:38
**Team notification (mandatory):** Always `@mention` `@elastic/observablt-ci` at the top of the issue body...

2. A prior autodoc-created issue shows the team handle rendered in backticks (non-pinging context):

elastic/oblt-aw#91 (issue body)
`@elastic/observablt-ci` please take ownership...

3. Upstream locked workflow used by autodoc explicitly states body mentions are neutralized:

elastic/ai-github-actions/.github/workflows/gh-aw-docs-patrol.lock.yml
line 325: - **Mentions**: `@mentions` in the body are neutralized (backticked).

4. Related historical change confirms intent focused on body mention requirement (now ineffective under neutralization):

• PR #101: “require @elastic/observablt-ci mention in generated issues for team notifications”

5. Cross-check from parallel investigations:

• No evidence of team slug typo drift in this repo (observablt-ci usage is consistent).
• Some other issue-producing routes have no explicit mention policy, which can also contribute to inconsistent behavior.

Verification

I ran targeted repository/metadata checks:

$ rg -n "observablt-ci|`@elastic`/|mention|mentions|team" .
# confirmed mention requirement in .github/workflows/gh-aw-autodoc.yml:38
# confirmed prior mention-related change in docs/workflows/gh-aw-autodoc.md:18

$ python - <<'PY'
# parsed upstream locked workflow fetched from elastic/ai-github-actions
# extracted relevant lines
...
208: Tools: create_issue, missing_tool, missing_data, noop
260: - Wrap branch names and @-references in backticks to avoid pinging users
325: - **Mentions**: `@mentions` in the body are neutralized (backticked).
PY

$ pytest tests/ -q
bash: pytest: command not found

(Last command indicates Python test tooling is not installed in this runner; investigation relied on static workflow/code evidence.)

Detailed Action Plan

1. Update autodoc workflow behavior in .github/workflows/gh-aw-autodoc.yml:

• Keep issue creation as-is.
• After audit creates an issue (needs.audit.outputs.created_issue_number != ''), add a notification step/job that posts an issue comment with plain-text cc @elastic/observablt-ci``.

2. Update docs in docs/workflows/gh-aw-autodoc.md:

• Replace “body mention notifies team” wording with: body mentions may be neutralized; notification is performed via follow-up comment.

3. Add a lightweight guardrail for issue-producing workflows:

• In wrappers that create issues, standardize notification policy (comment-based mention), including gh-aw-resource-not-accessible-by-integration-detector.yml where mention is currently conditional.

4. Validate in a test repository run:

• Trigger autodoc,
• Confirm issue is created,
• Confirm follow-up comment exists with the team mention in plain text.

5. (Optional hardening) Add a small reusable helper/workflow for “notify team on issue N” to avoid drift across workflows.

Related Items

Type	Link	Relevance
Issue	#144	Current report (“mention in issues not working”).
Issue	#91	Autodoc-generated issue showing handle in backticks in body.
PR	#101	Prior change that required body mention for notifications.
File	.github/workflows/gh-aw-autodoc.yml:18-39	Current autodoc prompt/instruction path.
File	docs/workflows/gh-aw-autodoc.md:18	Docs claim about body mention behavior.
Upstream workflow	elastic/ai-github-actions/.github/workflows/gh-aw-docs-patrol.lock.yml (line ~325)	Explicitly documents mention neutralization in issue body.

---

What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.