People make mistakes and if author change the permission and forget to
change it back, that can't be corrected by software (GIT). Git never knows
which file SHOULD be executable unless the author said so. The same as read
only.
My argument is: (keep read-only)
1. No harm
2. Do benefit s
The git GUI Create Branch dialog has some options at the bottom.
I cannot find any documentation on what these mean.
The first item in the Options is called "Update Existing Branch" and there
are three choices:
"No" , "Fast Forward Only", and "Reset".
What do these mean?
For what cases do they a
Yes, they are called deployment tools, which Git is not. One of the is
git-deploy[1], but there are more out there.
Also, I sense a design problem in your application if this is the case,
although it's hard to tell from this much information.
Best,
Gergely
[1] https://github.com/mislav/git-depl
Say you tell git-gui to create branch mybranch, but it already exists. If
update existing branch is turned off, it will be considered an error.
If you say fastforward or force, it will move your branch to HEAD (or the
commit iou specify). FF means it will move your branch only if it can be
done by
