I'd check out the links under "Bootcamp" here:

https://help.github.com/

On 12/4/2012 5:18 PM, Mark Pernotto wrote:
> As I'm clearly not well-versed in the goings-on of GitHub, I've
> 'forked' a response, but am not sure it worked correctly.
>
> I've zipped up and sent updates to Tom.  If anyone could point me in
> the direction of a good GitHub tutorial (for contributing to projects
> such as these - the 'creating an account' part I think I have down),
> I'd appreciate it.
>
> Thanks,
> Mark
>
>
>
> On Tue, Dec 4, 2012 at 1:43 PM, Tom Keays <[log in to unmask]> wrote:
>> Let's have mine be the canonical version for now. It will be too confusing
>> to have two versions that don't have an explicit fork relationship.
>>
>> https://github.com/tomkeays/issue-manager
>>
>> Tom
>>
>> On Tue, Dec 4, 2012 at 1:56 PM, Chad Nelson <[log in to unmask]> wrote:
>>
>>> Beat me by one minute Tom!
>>>
>>> And here it is in code4lib github
>>>
>>> https://github.com/code4lib/IssueManager
>>>
>>>
>>> On Tue, Dec 4, 2012 at 1:47 PM, Tom Keays <[log in to unmask]> wrote:
>>>
>>>> On Tue, Dec 4, 2012 at 1:01 PM, Shaun Ellis <[log in to unmask]>
>>> wrote:
>>>>
>>>>> You can upload it to your account and then someone with admin rights to
>>>>> Code4Lib can fork it if they think our Code4Lib Journal custom code
>>>> should
>>>>> be a repo there.  Doesn't really matter if they do actually. I think
>>> for
>>>>> debugging, it's best to point folks to the actual code the journal is
>>>>> running, which was forked from the official one on the Codex, right?
>>>>
>>>>
>>>> It was written for the Journal and originally kept in a Google Code repo
>>>> (this is before Github became the de facto). After the author left the
>>>> journal, he did a couple of updates which he uploaded to the WP Codex,
>>> but
>>>> nothing for a few years.
>>>>
>>>> Anyway, here it is:
>>>>
>>>> https://github.com/tomkeays/issue-manager
>>>>
>>>
>
>