CNA: be able to use CNA even if there is an existing README.md file

[chrisweb]

Goals

1. make it possible to use CNA even if there is already a README.md file present

Non-Goals

1. answer the question if we are alone in the universe

Background

When creating a new repository on github you get asked if you want a README.md file (if you check the box), then you go into VSCode, do a checkout of repository, run the CNA command, for example:

npx create-next-app@latest . --typescript --tailwind --eslint --app --turbopack --import-alias "@/*" --use-npm --no-src-dir

then CNA exists telling you the directory is not empty

so the idea behind this discussion is to brainstorm a solution that would make it possible to use CNA even if there is already a README.md file in the current directory

Proposal

here are some solutions:

1. to NOT create a READM.md file is there is already one
2. to let CNA first, rename the current README.md to something like PROJECT_README.md, and then create the next.js README.md as usual
3. to keep the current README.md of the workspace and create a new NEXTJS_README.md with the next.js content (it would also be possible to edit the current readme and insert a link to the next.js readme)
4. to merge the next.js readme content into the current readme, for example when you install sentry using the wizard, then they merge their own config into your existing next.config.ts, in a similar way we could merge the two README's
5. ask the user first what they prefer, like, do you want CNA to: "overwrite the current readme", to "merge both" or would you prefer "we backup the current readme and then add the CNA readme"