GitLab

Fixes #9237

Fixes #8732

See https://github.com/ohmyzsh/ohmyzsh/pull/7172#issuecomment-592875226

If I have custom configs (like theme customizations) I have to stash my changes and get them back after the update. 

By adding the --autostash on upgrade.sh, if I have any changes not commited they'll be reapplied after the upgrade, allowing me to have temporary customizations without any harm to the upgrade process.

Fixes #8416

* Change project URL from robbyrussell to ohmyzsh org

* Update git remote to use ohmyzsh org repository

- core.autocrlf=false -> #4069
- fsck.zeroPaddedFilemode -> #4963

Fixes #4069
Fixes #4963

* Updating Oh My Zsh shop URLs

Linking directly to the Oh My Zsh inventory vs the top-level store with non-OMZ items.

* Updating link to Oh My Zsh products in the install script

* Updating link to Oh My Zsh shop products in the upgrade script

* Getting rid of 't-' in shirts for now

When the user is asked to update oh-my-zsh it says "[Oh My Zsh] Would
you like to check for updates? [Y/n]:". When the user agreed to update
the next text would say "Upgrading Oh My Zsh" which is inconsistent
with the question.

@fcrozat's original fix assumes `which` not to output anything to STDOUT
in case the command is not found. That is not necessarily true on all
systems. A better solution is to check the return value instead.

Fixes #4376

Do not use terminal visual effects if not connected to a terminal.

After the upgrade is interesting to know what's new.

Changing the working directory in a sub-subshell
does not change the working directory of the executing
shell.

The substitution was broken for me on _all_ my machines,
so I started looking into the business.

If the current directory has spaces, the script fails to change paths and fails.

update.sh is an "sh" script, not a zsh or bash script. On platforms
which have real sh, echo does not have the -e option.

Make tools/install.sh and tools/upgrade.sh pretty.