Skip to content

fix: increase maxOutputTokens to prevent PR description truncation #126

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
robaone-redshelf merged 1 commit into from
Jan 5, 2026
Merged

fix: increase maxOutputTokens to prevent PR description truncation #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 8 additions & 6 deletions .github/actions/auto-release-description/generate_pr_description.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,19 +150,19 @@ ${diffContent}`;
* Create the main PR description prompt
*/
function createPRPrompt(diffContent) {
return `Write a release note summary with the following sections:
return `Write a release note summary with the following sections. Be comprehensive but concise - focus on the most important changes:

## Infrastructure Changes
Highlight changes to AWS resources, IaC (CloudFormation/SAM templates), Lambda functions, databases, and deployment configurations.
Highlight changes to AWS resources, IaC (CloudFormation/SAM templates), Lambda functions, databases, and deployment configurations. Use bullet points for clarity.

## Security Concerns
Identify any security-related changes, authentication/authorization updates, data access modifications, or potential vulnerabilities.
Identify any security-related changes, authentication/authorization updates, data access modifications, or potential vulnerabilities. If none, state "No significant security changes detected."

## Performance Implications
Assess any changes that could impact system performance, database queries, API response times, or resource consumption.
Assess any changes that could impact system performance, database queries, API response times, or resource consumption. If none, state "No significant performance implications detected."

## New Features
Describe new functionality, enhancements, or capabilities being introduced.
Describe new functionality, enhancements, or capabilities being introduced. Use bullet points for multiple features.

## Student Access Risk Analysis
Evaluate the risk that these changes could cause students to lose access to their course materials. Assess changes to:
Expand All @@ -178,6 +178,8 @@ function createPRPrompt(diffContent) {

If no student access risks are detected, state: "Risk Level: NONE - No changes affect student material access."

IMPORTANT: Keep the total response under 12,000 tokens. Be comprehensive but concise. Group similar changes together.

Print only the report and ask no questions.

${diffContent}`;
Expand Down Expand Up @@ -206,7 +208,7 @@ async function callGeminiAPI(prompt, apiKey, retryCount = 0) {
temperature: 0.7,
topK: 40,
topP: 0.95,
maxOutputTokens: 8192,
maxOutputTokens: 16384,
}
})
});
Expand Down