Maybe we should add some guideline for commit messages on git, I did something like this on my previous commit.

[Commit message]
Ticket #24 #19
- Did stuff 1
- Did stuff 2
[/Commit message]

The top line of a git commit message is always formatted as a title, so let us treat is as such. I've chosen to list the tickets I use and add a link to the tickets system.

Below the title I list up all the stuff that was accomplished on that commit.

Now what's kinda cool is that sourceforge was able to recognize the ticket numbers part of the message, in this case #24 and #19, and auto-formatted these numbers to hot-links to their specific tickets.

Great feature! Thanks for pointing that out. The number sign appears to be required in order for the hotlink feature to work. We should draft a standard operating procedure for interfacing with the git repo. A video tutorial would be nice as well.

Once I receive my workload for the week, I'll see what I can fit in and post it to the Sourceforge wiki and the forum.

_________________
Robert

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
"What good is knowledge and wisdom if you can't use it?" - Erasmus

Please review Game.agf for any changes before staging and commiting them. Game.agf is automatically updated with timestamps regardless if anything has been modified or not. Try to avoid pushing Game.agf if the only changes are the timestamps, since they cause a great amount of conflicts for poor Robert who has to process all the merge requests.