miniforge installation differs from expected

[sstevens2]

Testing the new mini-forge directions before my upcoming workshop. Installing on mac. It did not ask me to add to PATH instead it asked me to initialize conda base env automatically.

Do you wish to update your shell profile to automatically initialize conda?
This will activate conda on startup and change the command prompt when activated.
If you'd prefer that conda's base environment not be activated on startup,
   run the following command when conda is activated:

conda config --set auto_activate_base false

You can undo this by running `conda init --reverse $SHELL`? [yes|no]
[no]

I tried yes the first time and it errored out. The last line of the error message (below) seems to indicate it tried to use sudo. My account doesn't have sudo privs and so it errored out.

subprocess.CalledProcessError: Command '['sudo', '/Users/sstevens/miniforge3/bin/python', '-m', 'conda.core.initialize']' returned non-zero exit status 1.

I removed the miniforge folder and tried again, this time I said no to using the base environment and it still didn't ask me about adding to my PATH.