Closed therobut closed 11 years ago
I found this helpful https://help.github.com/articles/fork-a-repo And this http://www.youtube.com/watch?v=38ShL5YWigA&feature=channel&list=UL
What OS are you on. Since you are new to Git it might make sense for you to use a GUI client. GitHub itself provides ones for Mac and Windows.
I'm on linux (specifically Ubuntu).
I do tend to prefer command line for tasks that don't require a GUI and aren't overly complicated.
I'll check those links too thanks!
Also I use ZSH instead of bash and OhMyZsh for PS1 theming. I noticed that a lot of those themes include Git info which will be helpful I imagine
@archblob those links were exactly what i was looking for thank you!
Now since i'm new I'll ask one more question to be certain before I do anything. Is it proper etiquette to close this issue now that I got the answer I needed? Or should I leave it open in case others have the same question I did?
Well, i don't know what is considered proper etiquette but this beeing an "issue" that is now resolved, i think you should close it and if you consider it appropiate write a wiki entry about it.
alright thanks :)
Wiki page incoming
Hello everyone!
I'm a new developer with almost no experience. And I've never used Git Hub before. My only experience with Git itself is copy and pasting into my terminal to download things like OhMyZsh.
I saw in one of the other issues that it has been decided that the best way to move forward once code starts being committed, is to fork the project and submit pull requests.
It would be incredibly helpful if someone could write up just a real quick step by step for how to manage this process for noobs like myself to get a better grasp of what to do. Or maybe this has already been written elsewhere that I'm not aware of, so just a quick link to another page might suffice.
Thanks! And hopefully I'm not misusing the issues section here. :)