So I'm trying to figure out this Github thing...

[tg626]

Using MonoDevelop to compile my plugin I decided to try and stick it on GitHub. Last year, GitHub looked to intimidating to mess with, but now I'm trying to get it to work.

I finally uploaded my code to GitHub via the website and then managed to download it in MonoDevelop.

However when I make edits to my plugin and try to "Commit" it, it doesn't show up as changed in the website interface, even after 20 mins or so.

I can only assume I'm doing it wrong.  (Yes, I put in my name and password, and MonoDevelop seems to think it worked fine)

I also have no idea how "versioning" works - so in short I'm looking for help on this.  As always, I prefer a link to resources, but I'll take any advice I can get.  I had assumed it was all very nicely integrated and wouldn't require things like manually uploading it outside of the IDE once I got the git information setup properly, but maybe I'm expecting too much?

MonoDevelop 4.0.1, BTW

TIA!

[Jebman82]

Hi, I suggest you download the GitHub application for Windows or OSX. Then use the same folder for your mod/plugin. For example on Windows GitHub by default will save your repos to "My Documents" so copy/cut paste your code to that folder and work from there. Once done load up the GitHub application. It will detect changes automatically and ask you to commit them. Once committed *they will not appear on the GitHub website*. To make them appear you must "Push" or "Sync" the commit for it to go onto GitHub. In the application after you've committed your latest change you will see a sync button in the top left. Press it and you will see the changes on the GitHub website with your commit message.

All of the above can be done on the command line as well. While it is more complicated than above it is a useful skill to have:

https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/

In summary you:

1) Clone an old repo or create a new one

2) Add changes to your repo

3) Commit changes with a message explaining what is in the commit

4) Push the changes to master or another branch

When working with multiple developers you would then pull the master branch back after changes have been merged by someone else. This ensures you can work together.

Also once your base mod/plugin is ready, but you wish to add a new feature or fix something. Create a branch for the feature and work in isolation. Once your branch is tested and ready you can merge it into master. This means if another Dev forks your master branch they will be pulling a stable build and not something you're halfway working through.

Finally for some humour go to:

http://www.commitlogsfromlastnight.com

And see some funny commit messages from people who should have gone to bed and stopped coding!

 

Edited April 8, 2016 by Jebman82

[CobaltWolf]

Additionally, I made this video a while back to help someone. I'm not 100% sure that it all works the same though.

 

[tg626]

 

14 hours ago, Jebman82 said:

...them. Once committed *they will not appear on the GitHub website*. To make them appear you must "Push" or "Sync" the commit for it to go onto GitHub. In the application after you've committed your latest change you will see a sync button in g!...

 

That was the all important clue!!  Thanks for the info, links, etc. 

I find I can commit and push just fine from within Monodevelop so I'll stick to that.  Thanks a TON for pulling the gauze off my eyes so I could see clearly how it worked.

[Jebman82]

10 hours ago, tg626 said:

 

That was the all important clue!!  Thanks for the info, links, etc. 

I find I can commit and push just fine from within Monodevelop so I'll stick to that.  Thanks a TON for pulling the gauze off my eyes so I could see clearly how it worked.

No problem, happy to have helped!