Difference between revisions of "Talk:1296: Git Commit"
Line 1: | Line 1: | ||
Note that in most (all?) graphical history viewers for Git time flows from bottom up, i.e. newest commits are on top, not on bottom as in this comics --[[User:JakubNarebski|JakubNarebski]] ([[User talk:JakubNarebski|talk]]) 07:21, 27 November 2013 (UTC) | Note that in most (all?) graphical history viewers for Git time flows from bottom up, i.e. newest commits are on top, not on bottom as in this comics --[[User:JakubNarebski|JakubNarebski]] ([[User talk:JakubNarebski|talk]]) 07:21, 27 November 2013 (UTC) | ||
− | * This was bothering me. I was starting to doubt my own experience, and switch to an old project to check. — [[User:Kazvorpal|Kazvorpal]] ([[User talk:Kazvorpal|talk]]) 22:16, 18 December 2016 (UTC) | + | * This was bothering me. I was starting to doubt my own experience, and intended to switch to an old project to check. — [[User:Kazvorpal|Kazvorpal]] ([[User talk:Kazvorpal|talk]]) 22:16, 18 December 2016 (UTC) |
I can relate. While I start with reasonable commit messages every day, working on one feature often results in | I can relate. While I start with reasonable commit messages every day, working on one feature often results in |
Revision as of 22:16, 18 December 2016
Note that in most (all?) graphical history viewers for Git time flows from bottom up, i.e. newest commits are on top, not on bottom as in this comics --JakubNarebski (talk) 07:21, 27 November 2013 (UTC)
- This was bothering me. I was starting to doubt my own experience, and intended to switch to an old project to check. — Kazvorpal (talk) 22:16, 18 December 2016 (UTC)
I can relate. While I start with reasonable commit messages every day, working on one feature often results in
- (good description of feature)
- bugfixes for (description of feature)
- another bugfix
- damn
- should work now
- grrr
- typo
- I hate (some used library)
when I either need commit to deploy or I'm so sure it will work I don't test it deeply enough. If I would be using git, these could be merged, but I'm not. -- Hkmaly (talk) 10:51, 27 November 2013 (UTC)
What does the line graphic in the left-most column represent? Smperron (talk) 13:03, 27 November 2013 (UTC)
- This is the Git commit graph, in various ways of looking at a commit history git draws a graph like that to show branching and merging. 141.101.98.229 (talk) (please sign your comments with ~~~~)
Nice explanation folks. Makes the comic understandable/humorous to a non-coder. (unless you count VBScript) --DanB (talk) 13:16, 27 November 2013 (UTC)
- Nothing wrong with VBScript, though "coder" could be stretching the definition by a bit. (git it?) JChrisCompton (talk) 19:41, 5 December 2013 (UTC)
- You seem to understand it pretty well now, DanB, judging by your edit history. --Aaron of Mpls (talk) 07:56, 18 April 2014 (UTC)
Commit Cloud is a relevant tool to read commit messages from Github and build a word cloud from the most-used words. 108.162.214.41 (talk) (please sign your comments with ~~~~)
- Mine actually lists a link to this comic. I'm laughing so hard right now. Okofish (talk) 09:35, 13 January 2015 (UTC)
I'm very glad I'm not the only person this happens to. --Okofish (talk) 15:23, 27 November 2013 (UTC)
Regarding "although he seems to have avoided the ; key for some reason": A likely reason is that messages are passed on the command line with -m and without surrounding quotes to save time, and the ; ends the command line. 108.162.221.54 06:03, 1 December 2013 (UTC)