Skip to content

fix(generate): use commit subject as PR title and stop masking failures - #151

Closed
dodo-squirrels[bot] wants to merge 1 commit into
mainfrom
stlc-generated-33530756312
Closed

fix(generate): use commit subject as PR title and stop masking failures#151
dodo-squirrels[bot] wants to merge 1 commit into
mainfrom
stlc-generated-33530756312

Conversation

@dodo-squirrels

@dodo-squirrels dodo-squirrels Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Automated stlc build from config repo commit 5a81189507fa5b3732c5f2dce5308a786e88f217.

On 2026-09-01 the open_prs job reported success while opening ZERO of 9 SDK
PRs. Two independent defects combined:

1. pr_title was the FULL commit message. A 1039-char, 20-line body exceeded
GitHub's 256-char title limit, so createPullRequest rejected every call.
Now only the subject line is used, truncated to 256 chars.

2. The failure was swallowed by `|| echo "PR create skipped (likely already
exists / no diff)"`. That message was wrong by construction: the loop
already queries for an existing PR and only calls create when none is
found, so "already exists" cannot be the cause. The only benign failure
left is an empty diff; everything else now prints the real gh error and
fails the job.

The docs PR had the same masking pattern. Its branch is unique per run and
the no-diff case exits earlier, so any failure there is real -- it now fails
the job instead of logging a benign-sounding skip.

Verified against the actual message that broke it: 1039 chars -> rejected,
58-char subject -> accepted; a 411-char single-line subject truncates to 256.

Stainless-Generated-From: 966af95
@aagarwal1012

Copy link
Copy Markdown
Member

Closing: this branch forked from a base behind current main (behind_by=4), so merging it would revert the 1.115.0 release artifacts. It was produced by a workflow-validation run of stlc-generate.yml, not by a spec change.

@aagarwal1012
aagarwal1012 deleted the stlc-generated-33530756312 branch September 1, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant