From c189bc10bae24e79885b2aa74b71062506b6e7e4 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 16 May 2026 15:00:14 +0000 Subject: [PATCH 1/2] Initial plan From 73d4465f05babf24c6f832f11c4b251796b53cf9 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 16 May 2026 15:07:44 +0000 Subject: [PATCH 2/2] style: normalize daily function namer issue body header levels Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/daily-function-namer.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/daily-function-namer.md b/.github/workflows/daily-function-namer.md index 4939e043d6c..1d7e9d9ae08 100644 --- a/.github/workflows/daily-function-namer.md +++ b/.github/workflows/daily-function-namer.md @@ -251,6 +251,8 @@ If the state file was missing at the start of the run, initialize it from scratc If any rename suggestions were found across the analyzed package, create a GitHub issue. +Use h3 (`###`) or lower for all headers in the issue body. Never use h1 (`#`) or h2 (`##`) — these are reserved for the issue title. + If **no improvements were found**, emit `noop` and exit: ```json @@ -266,7 +268,7 @@ Otherwise, create an issue with this structure: **Body**: ```markdown -# 🏷️ Go Function Rename Plan +### 🏷️ Go Function Rename Plan **Package Analyzed**: `` **Analysis Date**: