Re: [oll-user] Git for dummies

[Janek W. <lem...@gm...>]

2014/1/11 Phil Holmes <ma...@ph...>

>
> > and I've already blundered.   I created a directory called
> > .../engraving-challenges and went there.  The files are now all a
> > directory
> >
> > .../engraving-challenges/engraving-challenges/
> >
> > but I suppose I can live with that for now.
>
> I pretty much always do that :-(
>

Yeah, git assumes you want to create a new directory with the repository's
name if you don't tell it otherwise.

You can specify the path where the cloned repository should be put, like
this:
git clone https://github.com/blahblah/blahblahpath/where/the/stuff/should/be/put

This way you don't even have to be in the directory were the clone will be
placed (the directory may not even exist yet).


> >>  Lunch beckons: let me know when you've done that.
> >
> > Yes!   I see I have a directory
> > .../engraving-challenges/engraving-challenges/challenge01/Mozart
>
> You should also see a number of other directories and files, for example
>
> engraving-challenges\challenge01\ chopin-godowsky.png
>
> (this was with Windows explorer for me - hence the \ / confusion.
>
> > Presumably I can put files there???    How do I upload them?
>
> Yes, you can put files into the Mozart directory, and git will recognise
> them there (probably).  git status will give you an idea of what's doing
>

a bit of git advice: git status is your best friend.  I used to run it
literally before and after every other command, until i learned enough that
i always knew what it will tell me.


> There's one  gotcha here: git has a list of filetypes it ignores in the
> .gitignore file,
> and by default .pdf is on this list - so if you're wanting to track and
> upload PDFs you'll need to edit .gitignore and get rid of the pdf entry.
>

This may not be a good idea: the .gitignore is part of the repository (git
actually tracks it).  You should rather add the file explicitely, i.e. 'git
add filename' (without using wildcards).


> OK - we've added *.png to the list of files being tracked: we now need to
> tell git to take a snapshot of the current situation.  We do this with a
> commit:
>
> git commit -am 'Commit message'
>
> a=all files; m=use this message.
>

a slight clarification: -a is "all tracked files".  It won't commit
untracked files if you haven't manually added them.

best,
Janek
-------------- next part --------------
An HTML attachment was scrubbed...