progit / progit2

Co-authored-by: Ben Straub <ben@straub.cc>

Co-authored-by: Ben Straub <ben@straub.cc>

Fix typo in section 2.4

Fix warning about `git restore` command

Add tip to point to the official GitHub CLI tool

The GitHub CLI lets you do your GitHub work from within the command line.
GitHub has just released version 1.0, and so we can "recommend" it to our readers.

…script-use-verbose-flags

Add tip: use verbose CLI flags for shared scripts

Git 2.23 comes with the experimental command `git switch`.
This commit adds a note with the most common operations that readers will want to use `git switch` for.

Warn readers not to throw away their local work without meaning to.
This is basically a copy/paste and adaptation of the warning we give about `git checkout -- <file>`.

…shing-amended-commits

Fix an article

Signed-off-by: Junjie Yuan <yuan@junjie.pro>

PowerShell on Linux requires the same escapeing of braces as on Windows

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>

Correct usage of braces vs brackets
Rewrite first sentence to flow better, and to explain the braces situation a bit better.
Remove "either" from the second sentence, as I think the sentence is better without that word. The "or" in the middle of the sentence makes it clear that there are two choices to deal with the bracket issue. So "either" is not really adding value.

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>

I've been struggling with the revision selection syntax `HEAD@{...}` and finally found out it's because of curly braces special meaning in PowerShell.

I noticed the NOTE on special handling of caret in cmd.exe on Windows. A similar note about curly braces in PowerShell would have saved me some time and I hope to save fellow developers some time by adding in such a note.

Thanks to HonkingGoose for his minor changes.

Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>

…mmits

…r-now

Explain missing .mobi builds in readme