5 ms·

I'm a beginner here so sorry for if it's a stupid question. I work with GitFlow and the only things I use are commits and checkouts, but for what do you use Git

by arrmn 11y ago

I'm a beginner here so sorry for if it's a stupid question. I work with GitFlow and the only things I use are commits and checkouts, but for what do you use Git? About which powerful features are you talking about, does anyone have a link with some more in depth informations?

on_and_off 11y ago
there are many 'minor' features that are occasionally useful. For example, when you make a stupid mistake, reflog can make you gain a couple of minutes.
camenk 11y ago
I think we use a lot of PR flow in our team. It's really powerful if you collaborate or plan to collaborate with others as it allows you to get together and look at the commits to ensure code quality (in theory). Even the command line git itself is really nice because it gives you the current condition of your repo and suggestion on what you can do next. You have changes, if you want to commit use this command or if you want to add use this command.
coldpie 11y ago
Some features I use: Cherry-picking commits across branches. Merging branches. Rebases for forward-porting your work onto a new upstream. Bisects for determining which commit introduced a bug. Push/pull for sharing. Format-patch for sending patches around. Submodules.
- pbowyer 11y ago
  Two of these I haven't done: Cherry-picking (well I did once, it went so wrong I had to reset the repository), and Bisects. That sounds very useful.
  - coldpie 11y ago
    If you want to get a deeper understanding of what git's doing, read gitcore-tutorial(7). It's pretty easy to understand git's internals, and once you know them, it's easier to understand what the user commands are actually doing. Then, if something goes wrong, it's much easier to recover.
krisgenre 11y ago
I am a guy who usually puts too much info into commit messages instead of code comments. Git blame recently helped me to find out why I had added a particular line to a lengthy if condition.
- gaius 11y ago
  Svn blame would have done the same... Where's the git-specific use?
  - krisgenre 11y ago
    Lol! Never knew svn blame existed :-). I suppose tracking a change over multiple merges may not be easy?
  - sandyarmstrong 11y ago
    As with many svn features, blame requires access to the server and is also quite slow. In git, this sort of thing is instantaneous and therefore viable to do all the time if you like.

by arrmn 11y ago

on_and_off 11y ago

there are many 'minor' features that are occasionally useful. For example, when you make a stupid mistake, reflog can make you gain a couple of minutes.

camenk 11y ago

I think we use a lot of PR flow in our team. It's really powerful if you collaborate or plan to collaborate with others as it allows you to get together and look at the commits to ensure code quality (in theory). Even the command line git itself is really nice because it gives you the current condition of your repo and suggestion on what you can do next. You have changes, if you want to commit use this command or if you want to add use this command.

coldpie 11y ago

Some features I use: Cherry-picking commits across branches. Merging branches. Rebases for forward-porting your work onto a new upstream. Bisects for determining which commit introduced a bug. Push/pull for sharing. Format-patch for sending patches around. Submodules.

pbowyer 11y ago
Two of these I haven't done: Cherry-picking (well I did once, it went so wrong I had to reset the repository), and Bisects. That sounds very useful.
- coldpie 11y ago
  If you want to get a deeper understanding of what git's doing, read gitcore-tutorial(7). It's pretty easy to understand git's internals, and once you know them, it's easier to understand what the user commands are actually doing. Then, if something goes wrong, it's much easier to recover.

krisgenre 11y ago

I am a guy who usually puts too much info into commit messages instead of code comments. Git blame recently helped me to find out why I had added a particular line to a lengthy if condition.

gaius 11y ago
Svn blame would have done the same... Where's the git-specific use?
- krisgenre 11y ago
  Lol! Never knew svn blame existed :-). I suppose tracking a change over multiple merges may not be easy?
- sandyarmstrong 11y ago
  As with many svn features, blame requires access to the server and is also quite slow. In git, this sort of thing is instantaneous and therefore viable to do all the time if you like.