How to add commit and push in git on mac

This compresses and otherwise Git-ifies the file, so that it's now in the freeze-dried format in the index, ready to be committed. Here, you must run git add: what git add does is to copy the work-tree file into the index. Now that you've changed these files, though, you might want your next commit to have the updated files. They're just files and they are totally under your control. You can replace files wholesale or edit them with editors or whatever you want. You can keep the line endings the same, or change them as you like. Now that all your files are in your work-tree, you can work on them as much as you like. There is only one conversion Git can do here on its own: it can turn newline terminated lines into CRLF terminated lines.

This last step-copy index file to work-tree-is when Git does end-of-line conversions. Then, having copied the commit to the index, Git now copies the index's files to the work-tree. Unlike the frozen files in commits, though, the copies in the index can be overwritten. That is: when you ask Git to check out a particular commit, what Git does is to copy 3 the files that are stored in that commit into the index. But for our purposes here, we only care about the fact that it sits between the committed files, and the work-tree copies of those files. In particular it's quite crucial when dealing with a conflicted merge. This thing-which Git calls, variously, the index, the staging area, or (rarely these days) the cache-actually has multiple functions. The index is perhaps best described, in one phrase, as the place where you build your next commit. The index sits between the commits and the work-tree :-) But most in general can't, and don't need to anyway. We haven't touched on the index yet, but it's time to do that.ДЎSome editors probably can, at this point: I'd be surprised if there is no GNU-emacs mode for viewing Git internal objects, for instance. gitattributes or tocrlf or any of these other options you can choose, Git only does them when copying files from the index to the work-tree, and when copying files from the work-tree to the index. And, when Git does file-format changes according to. The work-tree is not really part of the repository. Those are the files you will see and work with, and Git copies them into your work-tree: the area in which you do your work. These uncompressed and rehydrated files can be used by every program on your computer. They come out of the commit, going from the special, read-only, Git-only, freeze-dried format, to plain ordinary files. So, when you use git checkout to pick a particular commit, Git extracts these files. 1 They're great for archival and completely useless, at least on their own, for getting any new work done. The other programs on your computer, including your editors and file-viewers, cannot work with these files. The files inside each Git commit are stored in a special, read-only, Git-only, compressed form. It's just that they're all-the-commit, or none-of-it, at a time.

But commits themselves do store (snapshots of) files, so in that sense, Git stores files. And, in one sense, Git doesn't even store files, because the basic unit of Git storage is the commit. You do not work with files in the repository, because they're unsuitable for doing work. But we must distinguish between what's in the repository and what's in your work-tree. If you use the built-in conversions, that's what you'll actually get in your repository. You have to be kind of careful here, because Git has some built in conversions, and they strongly favor LF-only line endings.

How to add commit and push in git on mac