Remove link from CNCF announcement section

[aantn]

Removed link to GitHub issue comment from announcement.

[coderabbitai]

Walkthrough

Removed hyperlink from the announcement banner in the main HTML override template. The banner retains its static headline text but no longer includes the external link to CNCF Sandbox journey information.

Changes

Cohort / File(s)	Summary
Documentation template markup docs/overrides/main.html	Removed anchor element linking to CNCF Sandbox journey from announcement banner; banner content preserved as static text only

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Added announcement details #1057: Directly related—added the CNCF announcement link to the banner that this PR now removes, representing a reversal of that change.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Remove link from CNCF announcement section" directly describes the main change in the changeset. The raw_summary confirms that an anchor element linking to the CNCF Sandbox journey was removed from the announcement banner in docs/overrides/main.html. The title is concise, specific, and clearly conveys the primary action taken, allowing a teammate reviewing the commit history to quickly understand what was modified.
Description Check	✅ Passed	The pull request description "Removed link to GitHub issue comment from announcement." is related to the changeset. While the raw_summary specifies the link was to the CNCF Sandbox journey rather than explicitly a GitHub issue comment, both descriptions convey the same core change: a link was removed from an announcement section. The description accurately reflects the nature of the modification, and level of detail is not a factor for this lenient check.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch aantn-patch-1

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c34af2d and 6804ea3.

📒 Files selected for processing (1)

• docs/overrides/main.html (0 hunks)

💤 Files with no reviewable changes (1)

• docs/overrides/main.html

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Pre-commit checks
• GitHub Check: llm_evals
• GitHub Check: build

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Results of HolmesGPT evals

• ask_holmes: 34/35 test cases were successful, 0 regressions, 1 setup failures

Test suite	Test case	Status
ask	01_how_many_pods	✅
ask	02_what_is_wrong_with_pod	✅
ask	04_related_k8s_events	✅
ask	05_image_version	✅
ask	09_crashpod	✅
ask	10_image_pull_backoff	✅
ask	110_k8s_events_image_pull	✅
ask	11_init_containers	✅
ask	13a_pending_node_selector_basic	✅
ask	14_pending_resources	✅
ask	15_failed_readiness_probe	✅
ask	17_oom_kill	✅
ask	19_detect_missing_app_details	✅
ask	20_long_log_file_search	✅
ask	24_misconfigured_pvc	✅
ask	24a_misconfigured_pvc_basic	✅
ask	28_permissions_error	🚧
ask	39_failed_toolset	✅
ask	41_setup_argo	✅
ask	42_dns_issues_steps_new_tools	✅
ask	43_current_datetime_from_prompt	✅
ask	45_fetch_deployment_logs_simple	✅
ask	51_logs_summarize_errors	✅
ask	53_logs_find_term	✅
ask	54_not_truncated_when_getting_pods	✅
ask	59_label_based_counting	✅
ask	60_count_less_than	✅
ask	61_exact_match_counting	✅
ask	63_fetch_error_logs_no_errors	✅
ask	79_configmap_mount_issue	✅
ask	83_secret_not_found	✅
ask	86_configmap_like_but_secret	✅
ask	93_calling_datadog[0]	✅
ask	93_calling_datadog[1]	✅
ask	93_calling_datadog[2]	✅

Legend

• ✅ the test was successful
• :minus: the test was skipped
• ⚠️ the test failed but is known to be flaky or known to fail
• 🚧 the test had a setup failure (not a code regression)
• 🔧 the test failed due to mock data issues (not a code regression)
• 🚫 the test was throttled by API rate limits/overload
• ❌ the test failed and should be fixed before merging the PR