Skip to content

fix: mention workflow settings for Railway repos#866

Merged
exKAZUu merged 6 commits into
mainfrom
fix/agents-railway-workflow-instructions
Jun 10, 2026
Merged

fix: mention workflow settings for Railway repos#866
exKAZUu merged 6 commits into
mainfrom
fix/agents-railway-workflow-instructions

Conversation

@exKAZUu

@exKAZUu exKAZUu commented Jun 10, 2026

Copy link
Copy Markdown
Member

Customer Summary

  • Adds a Railway-specific generated agent instruction for repositories that use Railway.
  • Directs agents to .github/workflows when they need Railway project information.
  • Keeps the generated instructions tidy when optional guidance is not present.

Technical Summary

  • Adds isRailway to PackageConfig so Railway detection is centralized.
  • Detects Railway usage from package scripts, Railway marker files, and GitHub workflow contents.
  • Makes workflow scanning resilient to individual file read errors, case-insensitive for workflow extensions, and simpler by short-circuiting in one pass.
  • Updates the agent instruction generator to consume rootConfig.isRailway.

Why

  • Railway project details for WillBooster deployment workflows are managed in workflow settings, so agent instructions should point there when a repository uses Railway.
  • Centralizing detection on PackageConfig avoids duplicating repository detection logic in individual generators.

Testing

  • yarn verify
  • PR CI passed via bunx @willbooster-private/agentic-workflows@1.22.8 skills check-pr-ci

Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a check to determine if a project uses Railway (by checking package scripts, configuration files, or GitHub workflow files) and conditionally appends a Railway-related instruction to the agent's instructions. The review feedback suggests wrapping individual workflow file reads in a try-catch block within workflowFilesUseRailway to prevent a single file read failure from aborting the entire check.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread packages/wbfy/src/generators/agents.ts Outdated
exKAZUu and others added 2 commits June 10, 2026 11:51
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
@exKAZUu

exKAZUu commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces automatic detection of Railway projects by checking package scripts, configuration files (.railwayignore, railway.json), and GitHub workflow files. When a Railway project is detected, a corresponding instruction is appended to the agent generator. The feedback suggests pointing the agent to railway.json in addition to workflow files, as workflows might not always exist, and optimizing the workflow file check by using a case-insensitive regular expression instead of converting the entire file content to lowercase.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread packages/wbfy/src/generators/agents.ts Outdated
Comment thread packages/wbfy/src/packageConfig.ts Outdated
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
@exKAZUu

exKAZUu commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds detection for Railway projects and includes relevant instructions in the generated agent prompt. It introduces an isRailway property to the package configuration, which is determined by scanning package scripts, checking for specific files like .railwayignore or railway.json, and searching for 'railway' in GitHub workflow files. The review feedback suggests refining the agent prompt template to avoid introducing an extra newline when the Railway instruction is empty, and updating the workflow file regex to be case-insensitive to support uppercase YAML extensions.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread packages/wbfy/src/generators/agents.ts Outdated
Comment thread packages/wbfy/src/packageConfig.ts Outdated
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
@exKAZUu

exKAZUu commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces detection for Railway projects (isRailway) by checking package scripts, configuration files, and GitHub workflow files, and updates the agent instruction generator to include specific instructions for Railway projects and Playwright test servers. The review feedback suggests simplifying the workflow file detection logic in packageConfig.ts by combining .filter() and .some() into a single .some() call to eliminate redundancy, aligning with the repository style guide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread packages/wbfy/src/packageConfig.ts Outdated
Co-authored-by: WillBooster (Codex CLI) <agent@willbooster.com>
@exKAZUu

exKAZUu commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces detection for Railway projects and conditionally appends Railway-related instructions to the generated agent prompt. It adds an isRailway property to the package configuration, which is resolved by checking package scripts, Railway configuration files, or GitHub workflow files. I have no feedback to provide as there are no review comments.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@exKAZUu exKAZUu merged commit f9e5354 into main Jun 10, 2026
6 checks passed
@exKAZUu exKAZUu deleted the fix/agents-railway-workflow-instructions branch June 10, 2026 03:53
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