How to use github?

[endrick]

i opened an account there but i have no idea how to use it. Do you copy your codes and paste them there? or there is a way to upload your project so that others can use it and see how it works if you upload files of your project which one do you upload? the one with codes only? or the whole folder? i am learning c now but i don't know how to put my projects on github. help me out. thank you

[laserlight]

i opened an account there but i have no idea how to use it.

Generally, it is a good idea to read the manual before asking questions: GitHub Help

Do you copy your codes and paste them there? or there is a way to upload your project so that others can use it and see how it works if you upload files of your project which one do you upload? the one with codes only? or the whole folder? i am learning c now but i don't know how to put my projects on github. help me out.

If you had read GitHub's help pages, you would have seen:

At the heart of GitHub is an open source version control system (VCS) called Git. Git is responsible for everything GitHub-related that happens locally on your computer.

Basically, GitHub is a code hosting service intended for people to host their code (and other things) under version control in Git repositories. Hence, besides learning how to use GitHub, you need to learn how to use Git. I believe GitHub provides some guidance on how to use Git, but there are other resources available that focus on the topic, e.g., Pro Git book.

[Epy]

If you are on Windows, I suggest downloading GitHub Desktop and using that until you learn more about git. git is a severe pain in the ass and GitHub Desktop will take away some of the pain.

[MutantJohn]

Commit, pull, push. Boom.

[Aslaville]

Commit, pull, push. Boom.

Totally missed the essence of version control

[Yarin]

Commit, pull, push. Boom.

Tsk tsk, don't just go pulling and pushing what ever you like, be sure to request first.

[MutantJohn]

Totally missed the essence of version control

No such thing. Always rolling release. Git history. Boom. Bada bing!

[Mario F.]

No such thing. Always rolling release. Git history. Boom. Bada bing!

You are a pushover.

[MutantJohn]

You are a pushover.

Well, duh! That's how you get the rolling release to start rolling!

Edit: As a serious aside, I hope it was obvious that my posts were of a joking nature.

But I'm not sure what to say to the OP that laser didn't link to.

I think the basic commands were,

git add /whatever/stuff/you/have/
git commit -m "my commit message"
git pull
/* run tests to make sure nothing you pulled broke what you had */ 
git push

or at least, this is the git flow that I'm the most comfortable with. Yarin brought up a good point about doing requests. That would be something I'd do for a public project that I'd want to contribute to.

[Epy]

Yarin brought up a good point about doing requests. That would be something I'd do for a public project that I'd want to contribute to.

You're always talking about meshing--you should get involved with some of the projects concerning meshing, simulation, computational physics, etc.