git-autosave
An experiment in automatically backing up the working directory in a git repository whenever a file changes. (by nunull)
git-sync-changes
Collaborative editing for git repositories (by google)
| git-autosave | git-sync-changes | |
|---|---|---|
| 1 | 1 | |
| 0 | 38 | |
| - | - | |
| 10.0 | 10.0 | |
| about 6 years ago | almost 4 years ago | |
| Shell | Shell | |
| - | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-autosave
Posts with mentions or reviews of git-autosave.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-03.
-
Dura: You shouldn't ever lose your work if you're using Git
This is really cool. One drawback is that it seems to touch the index, which I believe should be avoided, since it can disrupt the users workflow. I experimented with something similar a few years ago and avoided the index. My learnings are partially documented in the repo.[1]
[1]: https://github.com/nunull/git-autosave
git-sync-changes
Posts with mentions or reviews of git-sync-changes.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-03.
-
Dura: You shouldn't ever lose your work if you're using Git
I built a similar tool a couple of years ago here: https://github.com/google/git-sync-changes
Both save uncommitted changes in a hidden ref.
The differences seem to be:
1. dura runs as a daemon while git-sync-changes is a one shot execution.
2. dura saves locally, while git-sync-changes syncs with a remote repo.
3. dura only does the save and the restore is manual, whereas git-sync-changes does both steps automatically.
I’m glad to see more people exploring this space. I think there’s a lot of untapped potential in tracking pending changes similarly to how we track committed changes.
What are some alternatives?
When comparing git-autosave and git-sync-changes you can also consider the following projects:
dura - You shouldn't ever lose your work if you're using Git
local-history - local-history for vscode
hiai - High Integrity Artificial Intelligence Systems