hiai
git-sync-changes
hiai | git-sync-changes | |
---|---|---|
1 | 1 | |
5 | 38 | |
- | - | |
10.0 | 10.0 | |
over 7 years ago | almost 4 years ago | |
Python | Shell | |
Apache License 2.0 | Apache License 2.0 |
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.
hiai
-
Dura: You shouldn't ever lose your work if you're using Git
I've also built a tool to support hyper-frequent commits, automatically rolling back the commit if the build, static analysis or any tests fail. This ensures a complete history of 'good/working' builds in the vcs.
https://github.com/wtpayne/hiai/blob/master/a3_src/h70_inter...
git-sync-changes
-
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?
dura - You shouldn't ever lose your work if you're using Git
local-history - local-history for vscode
git-autosave - An experiment in automatically backing up the working directory in a git repository whenever a file changes.