Commit log guide

[lukeab]

As stated in the podcast, we should manage the quality of input to the project, if Mike can't provide one, we should add one to the project ourselves.

[dominickm]

@lukeab not sure what you mean by commit log giude? Do you mean a format for commits? If so, I have a proposal:

SAMPLE COMMIT:

Commit Overview

details ....

[ghost]

What is going to be the commit model: fork and pull or shared resources?

[dominickm]

I think fork and pull would work best. As we progress I want to add others as maintainers, so I don't run out of bandwidth dealing all the pull requests. Not sure how we would break it up for maintainers. Perhaps one for master/staging and then ones for specific platforms / areas or interest?

[brentaar]

Vote for staging/master and cherry-pick into those branches.

[aaboagye]

dominickm, I like that method of having a maintainer for master/staging and others for specific platforms.

[dominickm]

@brentaar / aabogye

Yeah, so the way I think I am going to deal with this issue is as individuals commit more code to the project and show enthusiasm / confidence, I'll start looking for people to maintain the individual branches. That could be a little while.

Until then I just wanted to make sure our commits are the same in message format (pet peeve of mine) and scope.

[ghost]

@dominickm I know you said that you didn't want to have to tell someone to "RTFM" but I'm not sure about how to create lines in the comment. I've been using the git shell ( git commit -m "Commit Overview") how do I create new line in my comment argument?

I wanted to upload my test code with my UX Design(see requirements issue), I apologise if this is a stupid question. If any could help me, I would appreciate it.

[aaboagye]

@Daniel, what you can do is instead of using the -m flag, just type git commit and it will load your text editor where you can have multiple lines. Then save and quit and it will save your commit.

Daniel Samson reply@reply.github.com wrote:

@dominickm I know you said that you didn't want to have to tell someone to "RTFM" but I'm not sure about how to create lines in the comment. I've been using the git shell ( git commit -m "Commit Overview") how do I create new line in my comment argument?

I wanted to upload my test code with my UX Design(see requirements issue), I apologise if this is a stupid question. If any could help me, I would appreciate it.

---

Reply to this email directly or view it on GitHub: https://github.com/dominickm/jupiter_broadcasting_mobile_community/issues/1#issuecomment-6809320

Aseda Gyeke Aboagye

[ghost]

Thank you :)

[dominickm]

Sure, if you use git commit -a rather than -m. That should open your default editor (vim in most cases) where you can type as regularly ie with returns. Hope that helps.

Michael Dominick Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

On Friday, July 6, 2012 at 12:12 PM, Daniel Samson wrote:

@dominickm I know you said that you didn't want to have to tell someone to "RTFM" but I'm not sure about how to create lines in the comment. I've been using the git shell ( git commit -m "Commit Overview") how do I create new line in my comment argument?

I wanted to upload my test code with my UX Design(see requirements issue), I apologise if this is a stupid question. If any could help me, I would appreciate it.

---

Reply to this email directly or view it on GitHub: https://github.com/dominickm/jupiter_broadcasting_mobile_community/issues/1#issuecomment-6809320

[ghost]

It does seem to work well with windows...I just pushed my code up on to my fork https://github.com/Techfix/jupiter_broadcasting_mobile_community. I tried to write my comment inside notepad and saved it, Git just added comment.txt.

[dominickm]

@Techfix Ok great. I'll take a look at this. You should hear back from tomorrow.