3 ms·

I've shown coworkers "git log --graph --oneline --decorate --all -50" many times and always have them start with it (and even use it throughout stepping them th

by Izkata 3y ago

I've shown coworkers "git log --graph --oneline --decorate --all -50" many times and always have them start with it (and even use it throughout stepping them through something) to try and show that structure as we go. I think it helps a bit, but their IDEs go to great lengths to keep them out of the command line, so they're never completely sure what happened when it does something odd to their repo.

formerly_proven 3y ago
idk I clicked something and then there was an error so I deleted the project and started over
brabel 3y ago
> but their IDEs go to great lengths to keep them out of the command line Their IDEs can show them the graph you're talking about in a much richer form, lets them navigate through it, check what each commit did, who did it, and even change the graph (as everything in Git is changeable) by removing/rephrasing commits for example. I don't see how using the terminal actually helps anyone understand git, quite the opposite.
- Izkata 3y ago
  From what I've seen, they don't have that functionality. But my favorite is that it has a "sync" button for when a local and remote branch diverge due to a rebase, that doesn't tell you what it's going to do. The one time I saw it in use, it rebased new commits from master onto their branch.
  - brabel 3y ago
    IntelliJ: https://www.jetbrains.com/help/idea/investigate-changes.html https://www.jetbrains.com/help/idea/investigate-changes.html VSCode: https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph https://marketplace.visualstudio.com/items?itemName=mhutchie... or https://github.com/gitkraken/vscode-gitlens#commit-graph- https://github.com/gitkraken/vscode-gitlens#commit-graph- SourceTree: https://confluence.atlassian.com/sourcetreekb/viewing-log-history-of-a-repository-785615840.html https://confluence.atlassian.com/sourcetreekb/viewing-log-hi...
phforms 3y ago
I actually understood Git much better as soon as I switched from a graphical interface (which was Git Tower at the time) to just using the Git CLI. I feel like the graphical interface/overhead obscured what was really going on and made me not so much learn Git, but the tool on top of it. Git Tower is actually a great tool, but I believe Gits core concepts cannot be understood well without lots of experiments with the bare Git CLI (what helped me most was making toy repos → testing my hypotheses on how things work → observing/inspecting results).

by Izkata 3y ago

formerly_proven 3y ago

idk I clicked something and then there was an error so I deleted the project and started over

brabel 3y ago

> but their IDEs go to great lengths to keep them out of the command line Their IDEs can show them the graph you're talking about in a much richer form, lets them navigate through it, check what each commit did, who did it, and even change the graph (as everything in Git is changeable) by removing/rephrasing commits for example. I don't see how using the terminal actually helps anyone understand git, quite the opposite.

Izkata 3y ago
From what I've seen, they don't have that functionality. But my favorite is that it has a "sync" button for when a local and remote branch diverge due to a rebase, that doesn't tell you what it's going to do. The one time I saw it in use, it rebased new commits from master onto their branch.
- brabel 3y ago
  IntelliJ: https://www.jetbrains.com/help/idea/investigate-changes.html https://www.jetbrains.com/help/idea/investigate-changes.html VSCode: https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph https://marketplace.visualstudio.com/items?itemName=mhutchie... or https://github.com/gitkraken/vscode-gitlens#commit-graph- https://github.com/gitkraken/vscode-gitlens#commit-graph- SourceTree: https://confluence.atlassian.com/sourcetreekb/viewing-log-history-of-a-repository-785615840.html https://confluence.atlassian.com/sourcetreekb/viewing-log-hi...

phforms 3y ago

I actually understood Git much better as soon as I switched from a graphical interface (which was Git Tower at the time) to just using the Git CLI. I feel like the graphical interface/overhead obscured what was really going on and made me not so much learn Git, but the tool on top of it. Git Tower is actually a great tool, but I believe Gits core concepts cannot be understood well without lots of experiments with the bare Git CLI (what helped me most was making toy repos → testing my hypotheses on how things work → observing/inspecting results).