Cleanup New Connection Page

[strawgate]

Let's cleanup this page put the creds below the URL and maybe to have a single Advanced Settings section

[github-actions]

tl;dr: I recommend re-routing this issue to the playground app repository (or linking the owning path) because this repo does not contain a "New Connection" page implementation to change.

Recommendation

Treat #551 as likely misfiled for elastic/ai-github-actions and re-open it in the app repo that owns the connection UI (URL/credentials/advanced settings layout). If you want to keep tracking here, convert this issue into a docs/workflow task that points to the owning repo and adds a cross-link.

Findings

• Repo scope is workflow automation, not product UI:
  • README.md:3 — "AI-powered GitHub workflows for Elastic repositories."
  • DEVELOPING.md:7-11 — repository structure is workflow sources, compiled workflow files, and docs.
• The only in-repo references to connection UX are blog narrative about an external playground app, not implementation code:
  • docs/blog/posts/meet-the-smoke-testers.md:15-17
  • docs/blog/posts/meet-the-smoke-testers.md:21-25
• Related GitHub history check:
  • Issue search for "New Connection"/"Cleanup New Connection Page" in elastic/ai-github-actions returned only #551.
  • PR search for "New Connection" returned 0 results.

Verification

I ran targeted repo searches for the requested surface:

$ rg -n "New Connection|Advanced Settings" /home/runner/work/ai-github-actions/ai-github-actions
No matches found.

$ rg -n "New Connection|Advanced Settings|creds|credentials|URL" /home/runner/work/ai-github-actions/ai-github-actions/gh-agent-workflows
No matches found.

And in docs, matches are descriptive blog text about smoke tests, not editable UI page code:

docs/blog/posts/meet-the-smoke-testers.md:21
docs/blog/posts/meet-the-smoke-testers.md:23

Detailed Action Plan

1. Identify the owning repository/path for the connection dialog/page (the app referenced in docs/blog/posts/meet-the-smoke-testers.md:17).
2. Re-file this request in that repo with the same UX ask:
   • move credentials fields below URL
   • consolidate into one Advanced Settings section
3. Link the new issue back to #551 and close or relabel this issue as "external/misfiled".
4. (Optional, in this repo) add a short note in docs about where connection UI issues should be filed to reduce future misrouting.

Related Items

Type	Link / File	Relevance
Issue	#551	Triggering request
Search result	PR search "New Connection" in elastic/ai-github-actions	No matching PRs
File	README.md:3	Confirms repo scope
File	DEVELOPING.md:7-11	Confirms architecture/surfaces
File	docs/blog/posts/meet-the-smoke-testers.md:15-17,21-25	Mentions connection UX in external playground context

---

What is this? | From workflow: Trigger Issue Triage

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