Automatic checkins to local git repository (Sublime Text)
- Total 647
- Win 338
- OS X 203
- Linux 106
|Oct 16||Oct 15||Oct 14||Oct 13||Oct 12||Oct 11||Oct 10||Oct 9||Oct 8||Oct 7||Oct 6||Oct 5||Oct 4||Oct 3||Oct 2||Oct 1||Sep 30||Sep 29||Sep 28||Sep 27||Sep 26||Sep 25||Sep 24||Sep 23||Sep 22||Sep 21||Sep 20||Sep 19||Sep 18||Sep 17||Sep 16||Sep 15||Sep 14||Sep 13||Sep 12||Sep 11||Sep 10||Sep 9||Sep 8||Sep 7||Sep 6||Sep 5||Sep 4||Sep 3||Sep 2|
Automatic git checkins from your text editor saves.
autogit will automatically commit a version of a file to a local git repository everytime a change is saved in Sublime.
In windows, this is stored in
$(APPDATA)\autogit. In linux,
/usr/local/autogit. In OSX,
Why use autogit?
Some simple reasons:
- simple insurance against accidental changes or deletions.
- makes it easier to support smarter undo, backtracking, or exploratory programming.
- resume a task or track a task by seeing changes at a fine-grain level as they happened.
- light-weight, stays invisible until you need it.
Some deeper reasons:
Better Task Resumption: research suggests that resuming an interrupted task or reviewing a change made by another is made easier when changes can be reviewed in an time-ordered manner (in comparision to a flat commit).
Auto-blog: automark is a sister project that can examine a git repository and then automatically generate a markdown file, in a format suitable for publishing a blog post.
Personal Analytics: Watts Humphrey has advocated the idea of tracking personal activity for self-improvement, using methods such as the Personal Software Process. Using services, such as codealike or codeivate, you can track things like time spent editing, etc. Tracking the actual changes can take this analysis to another level.
Api Analytics: Frequent mistakes are made when programming or using particular apis. This can be analyzed: “You spent 3 hours figuring out how to correctly use pygit2.create_commit(), create github issue?”
See the main auto-git project for other editor support.