nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Trouble with Git

Theinsideman

I have a new job, with a shop that use git, i've never used it before and need to learn git quickly.

Im starting to freak because it seems so damn simple but for some unknown reason i cant get my head around it.

Can anyone please give me some advice on net sources, books etc. that helped them.

btw I dont have a problem technically with command line prompts its the methodology and logic that im struggling with.

Find more posts tagged with

Quick Links

Comments

KonFusion

Have you mentioned to be people in work that you're having trouble?

No need to freak. Just ask for help.

http://try.github.io/levels/1/challenges/1

Google is your friend. Tonnes of tutorials out there.

Theinsideman

KonFusion wrote: »

Have you mentioned to be people in work that you're having trouble?

No need to freak. Just ask for help.

http://try.github.io/levels/1/challenges/1

Google is your friend. Tonnes of tutorials out there.

Thanks for the link, not starting the job for another 4 weeks so i have time.

stevenmu

I haven't used Git in particular, but for source control generally, the easiest way to learn it is by doing it. It's definitely a good idea to have a read about it, and in particular look up some best practices and stuff, but don't worry too much if you don't totally get it. When you start there get some one to run through an example or two with you and it'll all become clear.

Keep in mind too that different places might have slightly different practices, in particular around things like branching/merging etc, so you will need someone there to run through that quickly with you anyway.

CrinkElite

I've only dabbled in some open source projects that use GIT but my first piece of advice is to ignore the GUI and use the GITshell

jester77

Forget about any GUI's, depending on what you are programming in, you might even have an IDE with a built in git integration... forget it. The only thing I use something like that for is to show me what branch I am on. Stick with the terminal and you'll be ok.

Here's is a good git reference, a quick reference and a cheat sheet.

KonFusion

Don't forget the git parable

Theinsideman

Thank you so much guys for all the advice. Very much appreciated.

[-0-]

Thanks to everyone on this thread. Git has now become fairly easy. I was merging everything to origin master...

After reading through this I have created a develop branch which makes way more sense.

Cheers!

Jonny Blaze

Found this simple guide a godsend when learning git under pressure.. http://rogerdudler.github.io/git-guide/

ChRoMe

Whats with all the GUI hate, its very rare that I wouldn't use IDE integration for source control. I find it a time saver having everything in one place.

srsly78

I find myself using command line AND gui. Gui is better for some operation, like committing a subset of files, holding ctrl-click to deselect some etc. Is handier for doing diffs. Command line is better for simple operations like a quick single file operation, it's faster than doing multiple clicks in a gui.

But yes, tortoisegit (or other gui) can be really annoying to setup because of ssh.

folan

i find myself using command line a lot of the time because i find it easier to use than intelliJ menus.

all in all, i used to use svn and preferred it to git, so my troubles might be coming from them being pretty different.