After months of looking, struggling through Git-SVN glitches and letting things roll around in my head, I’ve finally arrived at a web-focused Git workflow that’s simple, flexible and easy to use. Some key advantages: * Pushing remote changes automatically updates the live site * Server-based site edits won’t break history * Simple, no special commit rules or requirements * Works with existing sites, no need to redeploy or move files Overview The key idea in this system is that the web site exists on the server as a pair of repositories; a bare repository alongside a conventional repository containing the live site. Two simple Git hooks link the pair, automatically pushing and pulling changes between them.
Installation of package Work with git.el Customization The git-emacs package Installation and customisation Work with existing repository Creation of new repositories Work with changes History of changes Work with tags & branches The magit package Installation and customisation Basics of work with package Work with changes Work with history of changes Tags, branches, and remote repositories The egg package Auxiliary packages git-blame gitsum egit We can work with Git using several packages — either use modules for VC и DVC packages, or use packages git.el, emacs-git, magit & egg packages. In first case we work with Git through standard interfaces of VC & DVC.