Don't overwrite existing ahoy.yml on init #4
Assignees
Labels
Comments
|
This is a good idea, or at least have it check first, but you can actually update this yourself. If you implement an "init" command in .ahoy.yml, you can have it do (or not do) anything you want to. Example: commands:
init:
cmd: echo "These aren't the droids you're looking for.."
usage: Don't do anythingcommands:
init:
cmd: ls .ahoy.yml || wget $MY_INIT_FILE -O ./.ahoy.yml
usage: Download my own init file from elsewhere, but only if a local one doesn't exist.We should at least add that to the examples for now. |
|
This issue is still present in Ahoy 2 - running |
ocean
referenced
this issue
in ocean/ahoy
Jul 17, 2022
Shows a warning and a confirmation prompt when running `ahoy init` if an `.ahoy.yml` file already exists in the current directory and would otherwise be overwritten. BREAKING CHANGE: The warning prompt requires user input, so this may require updating of e.g. scripted calls to `ahoy init`. The prompt can be overruled by passing the "force" flag, e.g. `ahoy init --force`
ocean
added a commit
that referenced
this issue
Jul 25, 2022
fix!: [#4] Show overwrite warning for `ahoy init`
|
Closing as this is fixed with #97 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
initshould check for an existing .ahoy.yml file and prompt for overwrite before doing so.The text was updated successfully, but these errors were encountered: