-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git commit message suggestion #87
Comments
👍 |
which one you prefer @CMCDragonkai ? |
Karma's one seem pretty good. But we can use a strategy pattern. Basically we can have templating classes. One of them fits Karma, and people can extend it for further customisation and drill down. Also I don't think it should be called "Karma", just "default" templating. |
yeah @CMCDragonkai if you send a PR we will work on it, want to do that? I am excited, tonight we also merge support for BitBucket! |
Hey @cordoval you might have to wait for a bit for me to write a pull-request. Currently busy with other projects. Perhaps other people might take this suggestion up. |
oh we will do it before you can send a PR hopefully! thanks for your suggestion keep it up man! /o/ |
bump @CMCDragonkai wanna take a stab please? 👶 |
I reviewed the 3 links. are you saying we should have a command to commit? like gush p:commit?
This cycle repeats like n times every n PRs i do daily cc/ @lsmith77 |
let's dicuss this more in the context of the other tickets because we have to reach more integration ideas of the flows that we want to use/support. |
Which tickets are you referring to? And yes a commit command! |
not sure, lot of time has passed, try the editor helper on commit maybe, but think about the PR to make it useful. |
Would be great if Gush could setup a good git commit message formatting, such as text length (automatic new line) if the message is too long..etc.
Some ideas:
http://karma-runner.github.io/0.8/dev/git-commit-msg.html
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
http://stackoverflow.com/questions/15324900/standard-to-follow-when-writing-git-commit-messages
The text was updated successfully, but these errors were encountered: