Skip to content

[workflow-style] Normalize Daily Go Function Namer issue-body header formatting #32642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
May 16, 2026
+3 −1
Merged

[workflow-style] Normalize Daily Go Function Namer issue-body header formatting #32642

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c189bc1
Initial plan
Copilot May 16, 2026
73d4465
style: normalize daily function namer issue body header levels
Copilot May 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/daily-function-namer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -266,7 +268,7 @@ Otherwise, create an issue with this structure:
**Body**:

```markdown
# 🏷️ Go Function Rename Plan
### 🏷️ Go Function Rename Plan

**Package Analyzed**: `<package>`
**Analysis Date**: <YYYY-MM-DD>
Expand Down