Editing 1296: Git Commit
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
| β | This comic refers to the {{w|Git (software)|Git}} source code revision control software, which saves earlier versions of files and folders for later access into a special repository. This comes | + | This comic refers to the {{w|Git (software)|Git}} source code revision control software, which saves earlier versions of files and folders for later access into a special repository. This comes handy when you want to try out whether an idea works (branching). Further, you can collaborate with others by use of remote repositories. Perhaps most importantly, it allows members of the development team to find key changes in the history, later. Git has been discussed in [[1597: Git]] as well. |
A [[wikt:commit#Noun|''commit'']] is a saved version in a Git repository; a commit comes with a message that is supposed to describe what the commit contains, similar to the edit summaries used on {{w|MediaWiki}} sites such as ''[[explain xkcd]]'' and on [{{fullurl:{{FULLPAGENAME}}|action=history}} this explanation]. [[Randall]], however, finds himself losing interest in the commit messages the more code he writes and winds up just using placeholder text or jokes to himself. Presumably, this is because his separate commits are part of a large effort that can't be effectively summarized, and where there's no particular urgent need to differentiate the commits. Seeing as in this context 12 hours of coding can be considered "dragging on," it's safe to assume that the kinds of commits Randall is talking about are not for some major in-production project, nor for something that a lot of other people are working on. In both of those cases, one would be much more likely to use descriptive commit messages, since you want to flag things that are important, either from a technical standpoint (e.g. "fix the thing that's making the site not work") or for the benefit of others who want to know which commits they should be paying attention to. | A [[wikt:commit#Noun|''commit'']] is a saved version in a Git repository; a commit comes with a message that is supposed to describe what the commit contains, similar to the edit summaries used on {{w|MediaWiki}} sites such as ''[[explain xkcd]]'' and on [{{fullurl:{{FULLPAGENAME}}|action=history}} this explanation]. [[Randall]], however, finds himself losing interest in the commit messages the more code he writes and winds up just using placeholder text or jokes to himself. Presumably, this is because his separate commits are part of a large effort that can't be effectively summarized, and where there's no particular urgent need to differentiate the commits. Seeing as in this context 12 hours of coding can be considered "dragging on," it's safe to assume that the kinds of commits Randall is talking about are not for some major in-production project, nor for something that a lot of other people are working on. In both of those cases, one would be much more likely to use descriptive commit messages, since you want to flag things that are important, either from a technical standpoint (e.g. "fix the thing that's making the site not work") or for the benefit of others who want to know which commits they should be paying attention to. | ||
