git ff vs no-ff

Question

git

Which is better foast-foward or no-fast-foward?
It seems to me that it is better to use "no-fast-foward". But I read on the Internet that this is NOT a good form. Difficult to choose because I didn't have big project management in gith

Answer 1

Hello
As far as I understand, FF will only work if target is a child of the current commit.
In this case, nothing is broken, just the pointer is moved forward. The logic is saved.
If you need to switch to a commit from another branch, then FF simply won't work.
To be honest, I have not yet come across situations where it would be necessary to specifically refuse fast-forward

Answer 2

Use --no-ff to see all files in a branch.
Source