concept content in category git

appears as: contents, content, contents, content
Git in Practice

This is an excerpt from Manning's book Git in Practice.

Let’s view the contents of the new Git repository by changing to the directory containing the Git repository and running the find command.

To do anything useful in Git, you first need one or more commits in your repository. A commit is created from the changes to one or more files on disk. The typical workflow is that you’ll change the contents of files in a repository, review the diffs, add them to the index, create a new commit from the contents of the index, and repeat this cycle.

Listing 12.1. Good commit message format
Commits: first line is a summary (<51 characters). Commit messages should be structured like emails. The first line (the commit subject) should be treated like the subject of an email. It should make a brief summary that is elaborated on in the rest of the commit message. It should have 50 characters or fewer and always be separated by a new line from the rest of the commit message body. Without this new line, various output formats that try to display only the first line of the commit may get confused. The commit's message body can be split into multiple paragraphs which should be wrapped at 72 characters or fewer. The wrapping is done to ensure the output of tools like `git log` remains readable even when it adds indentation for diffs. Otherwise the commit message has no other limits on length; it should be as long as it needs to be to fully explain the commit. While the subject might describe what the commit does, the body should expand on why the change was made. It should also use the present tense to match the tense used by commit messages generated by commands such as git merge. If you're using GitHub (and some other tools) then the contents of commit messages can contain Markdown. You may use Markdown to add some formatting that looks good in ASCII or rendered such as using **bold**, _italics_, ~~strikethrough~~, `monospace` or lists bulleted with a `*` or numbered with, for example `1.`. You shouldn't go overboard with this but it can add some useful, basic formatting.