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: Jerry Krinock <email@hidden>
- Date: Fri, 31 Jan 2014 10:16:34 -0800
On 2014 Jan 31, at 07:56, Alexander von Below <email@hidden> wrote:
> There is a reason why "add" is different from “commit"
Yes, OK.
On 2014 Jan 31, at 09:29, Quincey Morris <email@hidden> wrote:
> 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.
I see the issue clearer now. New files which I’ve added to the project, typically source code files, are indicated as “A” and their checkbox is switched on by default. However, new files, typically resource files, which I’ve added to folders in the project are indicated as “?”. Apparently, Xcode is asking me whether I want to add these to source control or not. I’d like it to do that by default, but I can see why it might not.
>> P.S. I think that “Push to remotes” should be on by default too.
>
> 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.
No. It does not stick.
> ** I’m in the process of retraining myself not to use “Fixed lots of stuff” and “Save work in progress” as commit messages.
Oh, boy. You’re way ahead of me.
_______________________________________________
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