Re: Why does 'Commit' not add new files by default?
Re: Why does 'Commit' not add new files by default?
- Subject: Re: Why does 'Commit' not add new files by default?
- From: Quincey Morris <email@hidden>
- Date: Fri, 31 Jan 2014 09:29:47 -0800
On Jan 31, 2014, at 07:49 , Jerry Krinock <email@hidden> wrote:
Is there a good reason why those checkboxes are OFF by default? If not I'll file a bug.
In Xcode Preferences > Source Control, checkbox “Add and Remove Files Automatically” is on, but apparently that is for something different.
I have the checkbox on, and newly added files get an “A” status and are in the next commit. IIRC, this is new behavior in Xcode 5.0.x. Or a new preference default in Xcode 5. P.S. I think that “Push to remotes” should be on by default too.
It can’t work this way by default, because that would discourage you from committing often in a shared project — if you wanted to prevent your changes from being seen by collaborators until they were in a reasonable state, you’d have to put all of your changes into a big monolithic** commit.
OTOH, the checkbox setting does stick, doesn’t it? I’m pretty sure I tried it and it was on the next time I committed.
** I’m in the process of retraining myself not to use “Fixed lots of stuff” and “Save work in progress” as commit messages.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden