GitDoc is a Visual Studio Code extension that allows you to automatically commit/push/pull changes on save. This gives you the simplicity of a Google/Word Doc (creating "snapshots" by saving, not by running
git commit), but with the richness of git history, and the ability to easily share your work. You can enable these auto-commits during specific periods (e.g. when you're working on a feature branch and want to track the evolution of a change), permanently on specific branches (e.g. you have a
docs repo that you want to version like a document), or only for specific files (e.g. auto-commmit
*.md files, but nothing else). This allows you to easily switch between "versioning modalities", in order to support the diverse set of use cases that can benefit from being stored in a git repo (e.g. team projects, your personal blog, school work, etc.)
Commits are only created for error-free code, which allows you to author and save changes, knowing you aren't accidentally commiting invalid states. Additionally, just because you're auto-commmiting your changes, doesn't mean you lose control over your version history. When needed, you can easily restore, undo, and/or squash versions, without needing to memorize the magic of git. Additionally, you can opt into auto-pushing your changes to a remote, in order to treat your repo as a fully synchronized document source.
- Install this extension
- Run the
GitDoc: Enable command, and notice that your status bar now includes a
GitDoc button. This indicates that
GitDoc is enabled 🚀
- Open a file, make a change, and then save it
- Open the
Timeline view on the
Explorer tab (or run
git log), and within 30s, notice that a new commit was created on your behalf
- Select the top item in the
Timeline view to see the diff of the change you just made
- Continue to make changes, knowing that they'll be automatically tracked for you (as long as they don't contain errors) 👍
- At any time, you can restore, undo, and/or squash versions from the
Timeline, in order to "clean" up/manage your history
- When you're done, simply click the
GitDoc button in your status bar, run the
GitDoc: Disable command
From here, you can permanently enable auto-commits for an entire repo or branch, customize the files that are auto-committed, and even auto-push your changes in order to keep your repo fully synced.
By default, when you enable
GitDoc, it will create commits every 30s, whenever there are actually changes. So if you don't make any changes, than it won't make any commits. However, if you're continuously writing code, then it's only going to capture those edits in 30s intervals. This way, you don't generate a massive number of commits, depending on how frequently you save files. If you find that 30s is too short or too long, you can customize this by setting the
GitDoc: Auto Commit Delay setting to the appropriate value.
In addition to automatically creating commits, GitDoc will automatically push your changes to the configured remote. By default, changes will be pushed as soon as you commit them,but this can be configured via the
GitDoc: Autopush setting. This can be set to
afterDelay in order to push on some sort of frequency (controlled via the
GitDoc: Auto Push Delay setting, which defaults to
30s). Additionally, if you don't want to auto-push changes, you can disable this behavior by setting the
GitDoc: Autopush setting to
Note: When you enable this, GitDoc will actually perform a
git push --force, since certain operations such as
squashing can actually re-write history.
By default, when you enable
GitDoc, it will automatically pull changes from the repo when you 1) open the workspace, and 2) push changes. This ensures that your local copy is in sync with the remote, and attempts to mitigate merge conflics from happening. If you'd like to modify this behavior, you can customize the
GitDoc: Auto Pull and
GitDoc: Pull on Open settings.
By default, auto-commits are only made when a file is changed, and it doesn't have any pending errors (e.g. issues in the
Problems panel with an
error severity). This prevents you from creating commits that represent invalid changes, and allows you to install whatever linting/testing/build extensions you want, knowing that they'll "gate" your auto-commits. If you want to suppress commits in the presence of warnings, or ignore problems entirely, and simply always auto-commit, then you can set the
Commit Validation Level setting to
When you enable
GitDoc, it creates a new commit anytime you save a file. This allows you to control when commits are created, simply be determining when you save. You can save a single file, or multiple files, and all of the changes within a single "save operation" will be committed together.
If you'd like to automatically track your changes, without needing to explicitly save, then simply set the
Files: Auto Save setting, specifying the exact behavior you'd like (e.g. save every 30s).
Auto-commiting specific branches
In addition to enabling
GitDoc during temporary periods, you can also choose to enable it on specific branches, in order to automatically track your work for as long as you're using the branch. Simply switch to the desired branch and run
GitDoc: Enable (Branch).
Auto-commiting specific files
If you'd like to only enable auto-commiting for specific files, you can set the
GitDoc: File Pattern setting to a file glob. For example, you could set this to
**/*.md in order to auto-commit markdown files, but nothing else. By default, this is set to
**/*, which auto-commits changes to any file.
When this setting is set, the
GitDoc status bar which only appear when you have a file that is matches it. This way, you can easily tell when you're editing a file that will be auto-committed/pushed.
Auto-committing is useful for tracking unique versions, however, depending on how frequently you save, you could end up creating a significant number of file versions. If a series of versions represent a single logical change, you can "squash" them together by right-clicking the oldest version in the
Timeline tree and selecting the
Squash Version(s) Above command. You can give the new version a name, and when submitted, the selected version, and all versions above it, will be "squashed" into a single version.
Demystification: Behind the scenes, this command performs a
git reset --soft, starting at the commit before the selected one. It then runs
git commit -m <message>, where
message is the string you specified. This preserves your working directory/index, while "rewritting" the commit history.
If you've made a bunch of changes to a file, and want to restore an older version, simply open up the
Timeline tree, right-click the desired version, and select
Demystification: Behind the scenes, this command peforms a
git checkout -- <file> (on the file that's associated with the selected timeline item), followed by
git commit (in order to commit the restoration). This way, the restore is a "forward moving" operation.
If you made a change, that you want to undo, you can simply open up the
Timeline view, right-click the version you want to undo, and select
Undo Version. This will create a new version that undos the changes that were made in the selected version. This way, any undo action is actually a "forward edit", that you can then undo again if needed.
Demystification: Behind the scenes, this command simply performs a
git revert on the selcted commit. Because this is a "safe" action, you can generally perform it without any problems (including on shared branches), since it doesn't re-write history.
GitDoc is enabled, it will contribute a status bar item to your status bar. This simply indicates that it's enabled, and makes it easier for you to know which "versioning mode" you're in (auto-commit vs. manual commit). Additionally, if you enable auto-pushing, then the status bar will indicate when it's syncing your commits with your repo. If you click the
GitDoc status bar item, this will disable
GitDoc. This allows you to easily enable GitDoc for a period of time, and then quickly turn it off.
When you install the
GitDoc extension, the following commands are contributed to the command palette, and are visible when your open workspace is also a git repository:
The following settings enable you to customize the default behavior of
GitDoc: Auto Commit Delay - Controls the delay in ms after which any changes are automatically committed. Only applies when
GitDoc: Enabled is set to
true. Defaults to
GitDoc: Autopull - Specifies whether to automatically pull changes from the current remote. Can be set to one of the following values:
off. Defaults to
GitDoc: Autopull Delay - Controls the delay in ms after which any changes are automatically pulled. Only applies when
GitDoc: Auto Pull is set to
afterDelay. Defaults to
GitDoc: Autopush - Specifies whether to automatically push changes to the current remote. Can be set to one of the following values:
off. Defaults to
GitDoc: Autopush Delay - Controls the delay in ms after which any commits are automatically pushed. Only applies when
GitDoc: Auto Push is set to
afterDelay. Defaults to
GitDoc: Commit Message Format - Specifies the moment.js format string to use when generating auto-commit messages. Defaults to
GitDoc: Commit Validation Level - Specifies whether to validate that a file is free of problems, before attempting to commit changes to it. Defaults to
GitDoc: Commit on Close - Specifies whether to automatically commit changes when you close VS Code. Defaults to
GitDoc: Enabled - Specifies whether to automatically create a commit each time you save a file.
GitDoc: File Pattern - Specifies a glob that indicates the exact files that should be automatically committed. This is useful if you'd like to only auto-commiting specific files, as opposed to an entire branch.
GitDoc: Pull on Open - Specifies whether to automatically pull remote changes when you open a repo. Defaults to