I found the Netlify CLI pretty exasperating to use. In addition to it just being straight up information overload at any given step, the feedback it does print

I found the Netlify CLI pretty exasperating to use. In addition to it just being straight up information overload at any given step, the feedback it does print out is often misleading or the opposite of helpful in some other way. More from my notes on that day: > My use case is to deploy a static site. I have a directory containing the pages. I've installed the Netlify CLI (itself a stupidly fiddly process). [And I've read the docs by now.] I should be able to init and deploy, trivially, right? Wrong. Without even trying I ran into some crash bugs in the CLI, for what seems to be a bog-standard use case. On a hunch, I decided to check what would happen if I moved the .git subdirectory somewhere else and re-ran. And whaddaya know, I found that it worked reliably when there was no .git subdirectory anywhere to be found, and it reliably failed when it was present. So even though the contents of .git/ are completely irrelevant for the use case, the CLI is evidently both (a) trying to do something with it, and (b) making some bold assumptions about what's in there and failing hard. My money is on "Nobody at Netlify is even testing this." (FWIW, no I didn't report this. The overall "feel" of their stuff leads me to believe it would be a painful experience with no upside. Several years ago, I interacted with some Netlify folks early after their launch to give some feedback that was more of the sort "I'm reaching out to inform you of a problem for your own benefit and help you resolve it" than it was anything like "I'm here to get you to help me with my problem". The overall tone of the responses were pretty obnoxious under those circumstances, so I noped out and never gave them any serious consideration until this year, where I discovered the situation above. I have to say it pretty much validated my early opinion.)