Repository navigation
Conversation
Retasusan
marked this pull request as ready for review
September 13, 2026 08:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add support for configuring default Ruby and Rails versions, along with reusable
rails newarguments, through a TOML configuration file.Motivation
Users who consistently generate applications with the same Ruby version, Rails version, or
rails newoptions currently need to repeat those flags for everyinvocation.
This change allows those defaults to be stored in:
When XDG_CONFIG_HOME is set, rails-new reads:
On Windows, it falls back to:
Example
With this configuration:
rails-new myapp
uses the configured Ruby and Rails versions and passes the configured arguments to rails new.
Explicit command-line values take precedence over configured defaults:
Configured rails_args are inserted after the application path and before additional command-line arguments.
If the configuration file does not exist, the existing behavior is preserved:
Unknown configuration keys and invalid TOML produce an actionable error instead of being silently ignored.
Validation