Skip to content

bin/dev file collision, could it be prevented ? #146

@bdavidxyz

Description

@bdavidxyz

Use case : create a new rails application

rails -v
7.1.2
rails new theapp --force --database=postgresql -j=esbuild -c=tailwind --skip-docker

Will result, despite the "force" option, into an interrupt :

       rails  css:install:tailwind
       apply  /home/david/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/cssbundling-rails-1.3.3/lib/install/install.rb
(...)
      append    Procfile.dev
  Add bin/dev to start foreman
    conflict    bin/dev
  Overwrite /home/david/workspace/railsback/flow/theapp/bin/dev? (enter "h" for help) [Ynaqdhm] a

Not a big deal for a simple "rails new" command, but still annoying in many scenario when you have to generate rails skeleton (template) apps, interrupting the build flow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions