@TravisEz13 - I can't recall what to do about spelling errors in MD files - can you please remind me what we did last time?

You need to add the missing words in this section https://github.com/PowerShell/PowerShell/blob/master/.spelling#L215

@TravisEz13 - Looks like this is failing at the OSX sudo password prompt? How to handle this? Thanks! https://travis-ci.org/PowerShell/PowerShell/jobs/380487406

@DarwinJS SUDO -v almost never works in CI. You'll have to update the code to skip this check. Or remove it altogether as unreliable.

Is there a way to detect CI? Is checking for POWERSHELL_TELEMETRY_OPTOUT=1 good enough or is there a better way?

There have not been any complaints about the sudo check (that I know of) beyond CI.

FYI - I updated the sudo check to be non-interactive.

most CI systems, except VSTS define a variable called CI. You can just doc that you expect that variable to be defined.

@TravisEz13 - I put in place the skipping of the sudo check, but also skipped sudo assuming I had admin.

So is the magic that I DO need to use SUDO - but I can't check for it?

How has this not been failing for months - it used to work without any special SUDO handling, but didn't break until I touched it.

Can you look at the build log?

My statement about sudo -v never working was too broad. It never worked in macOS, but other CI systems it doesn't work in debian. When in CI, we need to use sudo but not run sudo -v as it may fail. The equivalent of skip-sudo-check, these other systems is what I added this switch for. Just detecting CI and automatically skipping should be enough.

Also, you should look at the package renaming during preview.3 and see if this affects your change.

@TravisEz13 - builds are passing - should I remove "WIP" ?