From 8c40fed0f5638ddffcf2f56bf5d1f4a724cf240f Mon Sep 17 00:00:00 2001 From: Dave Wilding Date: Tue, 25 Aug 2026 21:59:32 +0800 Subject: [PATCH] Increase .PR.md title limit from 70 to 100 characters MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The agent wrote a 72-char title (72, just 2 over the 70 limit) and the run failed. 70 was a constraint from the old JSON format where title length mattered for single-line parsing. With the .PR.md approach, GitHub PR titles can be up to 256 characters — 100 is a reasonable limit that gives the agent room for descriptive titles without being excessively long. --- .github/scripts/probe_issue.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/scripts/probe_issue.py b/.github/scripts/probe_issue.py index ebfdfac..0e33f61 100644 --- a/.github/scripts/probe_issue.py +++ b/.github/scripts/probe_issue.py @@ -486,7 +486,7 @@ def test_deploy(charm, juju: jubilant.Juju): document: - The first line must be a `# ` heading containing the PR title — a short \ -phrase, not a full sentence. Must not exceed 70 characters. Examples: \ +phrase, not a full sentence. Must not exceed 100 characters. Examples: \ "Try foo in bar tests", "log_level filters DEBUG from captured logs". - Everything after the title heading is the PR body. Enumerate the claims \ you identified (A, B, C), state which you tested and why, what you believe \ @@ -708,9 +708,9 @@ def read_pr_description(repo_root: Path) -> dict[str, str]: title = title_match.group(1).strip() if not title: raise ValueError(f"{PR_DESCRIPTION_FILENAME} heading must not be empty.") - if len(title) > 70: + if len(title) > 100: raise ValueError( - f"{PR_DESCRIPTION_FILENAME} title must not exceed 70 characters " + f"{PR_DESCRIPTION_FILENAME} title must not exceed 100 characters " f"(got {len(title)})." )