Skip to content
Snippets Groups Projects
Verified Commit 23820c80 authored by ck85nori's avatar ck85nori :railway_track:
Browse files

improves ui notes

parent e95c096e
No related branches found
No related tags found
No related merge requests found
...@@ -358,8 +358,11 @@ ...@@ -358,8 +358,11 @@
notes: notes:
- learn by doing / understand what you do - learn by doing / understand what you do
- gui hides too much of that - GUI hides too much of that
- use gui if gui helps workflow - use GUI only if it integrates well in your workflow, e.g. IDE
- my main editor is emacs, so I'm using emacs integration (magit)
for most of my day-to-day tasks, only a few key presses per git
operation, when I'm in the terminal, I simply use the CLI
</section> </section>
<section id="cli-description" data-markdown> <section id="cli-description" data-markdown>
...@@ -525,6 +528,8 @@ ...@@ -525,6 +528,8 @@
- **prepare** commit adding more and more **changes** - **prepare** commit adding more and more **changes**
- **commit** this **set of changes** - **commit** this **set of changes**
- commit **should be a logical unit** of changes - commit **should be a logical unit** of changes
- the deciding feature of a git (G)UI is how it handles the stage,
i.e. if you can't interactively stage/unstage hunks, the UI sucks
</section> </section>
<section id="cli-git-files" data-markdown> <section id="cli-git-files" data-markdown>
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment