The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Lets make sure pkfox has the basics down solid before going into advanced features with elevated footgun potential.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
cool! I'm glad it worked for you. It was off the top of my head so I wasn't sure if maybe i forgot a step or something, but then you got it working so i figured no harm, no foul.
I like to keep it simple with github.
The only wrinkles you might want to know about now:
A) if you create a public repo, make a README over at github, then sync from VS to pull it into your local project copy.
B) if you build your binaries to a custom folder they'll be uploaded to github as it only ignores the bin and obj folders in the default locations last i checked. You might consider this a feature, or a bug depending on how you feel about it.
(Ignore the fact that this is for TortoiseGit - the concepts are the same.)
Git pull is a git fetch followed by git merge
Git fetch fetches info about remote repositories
Git sync does everything in one command meaning pull and push
The link above includes "read more" links for further reading.
And as others have said, cloning is used only when the repo doesn't already exist on the machine.
I prefer pull rather than sync because I want to push in a controlled manner -- only when my code compiles and is tested. There are many times when I have my code with compiler errors or it's in a "work in progress" state, so I'm not ready to push it up, as this will probably break other people's stuff. However, sometimes I do need to pull down other people's stuff while I'm working on my own.
If I want other people to see my "work in progress", I'll create a local branch for my changes, then push that branch. That way, I'm not messing up the master and other branches (like qa, test, etc.)
Similarly, if someone has a special branch that I want to look at, I'll do a fetch to see that branch in the list of repo branches, then do a "check out" of that branch to my local machine.
One thing that took me a while to understand about git.
It treats the ENTIRE repository as image, for lack of a better word, so if you have a file in your current branch that does not exist in a different branch, and you switch branches that file will vanish. Worry not! It is not gone because if you switch back to the original branch the file will reappear.
I missed your earlier Github posts (I assume) but am in a similar place. Normally working on my own, I'm now working on a project jointly (and remotely) with another development house. In the past I've always used SVN (With TortoiseSVN and a remote repository) which has been simple and met my purposes. My associates now want us to use Git to better manage concurrent developments, and am having probs getting my head around concepts (partly as there's so much additional terminology). Have setup a remote repo and done an initial push, but am a way behind you on the learning curve. Very re-assuring to know I'm not the only one, though! This thread looks like the answers will be very useful.
Seriously though, I can get like that.
Also when talking or performing for groups, doing important sales calls or having bad news conversations.
I've found that beta-blockers work great
Avoiding all social contact works even better and I've heard it's all the rage nowadays
Never for exams though, so I've got that going, which is nice.