* Update Git workflow 1.2 Make changesi
- Advise to use add --patch
- Switch to use commit without --all
* Fix space
* Change usage for git add
- Describe specifying file list
- Include --patch as tip
The word "imperative mood" (Meireiho; 命令法) in the source language was translated as "subjunctive mood"(Kateiho; 仮定法) in Japanese by mistake. Both moods is different in English linguistics. The translation should be fixed.
Vim creates swap files when open buffers are edited.
These files preserve un-written changes in buffers. They are useful for
recovering from system crashes, preventing multiple write-buffers on a
single file (which could cause "phantom-edits"), etc.
However, these swap files should not be tracked in a git repository.
For a given working file, Vim will create a swap file of the format
`<filename>.swp`.
Vim will attempt to remove swap files upon writing & exiting Vim.
However, swap files aren't always cleaned up. This may happen if Vim
terminates improperly due to a system crash or similar.
So, if Vim attempts to create a swap file of the format
`<filename>.swp`, but that path already exists, then Vim will create a
swap file of the format `<filename>.swo`.
If `<filename>.swo` already exists, then Vim will create a swap file
`<filename>.swn`.
Vim will continue backwards through the alphabet until it finds an
available swap-file path.
If `<filename>.sw[a-p]` is completely occupied, then Vim will attempt
`<filename>.sv[a-z]`, and so forth.
However, I did not include `*.sv[a-z]` in this change because I believe
that would be overkill, and it may trespass on other programs.
I am reasonably certain that no other programs rely on `*.sw[a-p]`
files. I am less certain about `*.sv[a-z]` files.
Also, having that many swap files is a rarity. The disadvantages of
including `*.sv[a-z]` in the .gitignore outweigh the benefits.
So, I only included `*.sw[a-p]` files in this change.
The current validation using `allow` will allow any kind of string, not only the specified ones.
`NODE_ENV=foo` is totally valid. Using `valid` instead should fix this.
1. Remove invalid whitespaces.
2. Fix some fatal translation.
3. Add some extra relevant words when translating(the Git part) to make it mostly like native Chinese speaking.
1. Localize more symbols like colon and period.
2. Improve some translation especially the section of Git.
3. Sync the doc with the English one.
4. Translate 'you' into Chinese using the honorific instead of the mixed usage.
* initial commit adding git hooks under section 7 (code style)
* add a section on code style check within the editor
* add a section on using prettier with pre-commit hooks using husky
* update links
* reformat section to follow existing flow
* 👌 make changes and update links
* follow current text format and remove redundant point
* translation part one
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* use [中文版](./README-zh.md)
* remove readme.html
* fix some grammar
* fix some letter
* fix the article
* update document
* Add new logo
* Rename logo file
* Fix file name typo
* Make logo smaller
* Add icons
* Add branching image
* Set the branching image right
* Add icons to both english and chinese
* Fix logo and add link to english
* translation part one
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* use [中文版](./README-zh.md)
* remove readme.html
* fix some grammar
* fix some letter
* fix the article
* translation part one
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* use [中文版](./README-zh.md)
* remove readme.html
* fix some grammar
* translation part one
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* add more
* use [中文版](./README-zh.md)
* remove readme.html
