dura
git-sync-changes
dura | git-sync-changes | |
---|---|---|
11 | 1 | |
4,250 | 38 | |
- | - | |
1.4 | 10.0 | |
7 months ago | almost 4 years ago | |
Rust | Shell | |
GNU General Public License v3.0 or later | 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.
dura
-
Script for creating snapshot commits on a not checked-out branch without touching the working tree
This is just a tiny Bash script, but I feel like it might be useful to someone other than myself. It's basically a poor man's Dura (https://github.com/tkellogg/dura) that is triggered manually instead of using a background process and a timer.
-
Autosaved puts an end to the developer anxiety caused by uncommitted Git changes
There is an existing alternative called Dura by the way. https://github.com/tkellogg/dura
-
Utility that autosaves uncommitted changes in your Git repositories so that you don't accidentally lose them
A very similar utility, Dura, was posted last week on Hacker News. Not sure if it does the exact same thing, but FYI https://github.com/tkellogg/dura
-
Dev Genius: Have you head of Dura yet? 2022's upgrade for Git
If you'd prefer, directly check out Dura's GitHub repo here:
https://github.com/tkellogg/dura
- Dura
- Dura - Your Personal Git Safety Net
- GitHub - tkellogg/dura: You shouldn't ever lose your work if you're using Git
- Dura is a background process that watches your Git repositories
- dura - You shouldn't ever lose your work if you're using Git
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?
git-autosave - An experiment in automatically backing up the working directory in a git repository whenever a file changes.
local-history - local-history for vscode
hiai - High Integrity Artificial Intelligence Systems
git-snap - Create snapshot commits on a not checked-out branch without touching the working tree or losing staged changes
git-cache-tag
autosaved - Never worry about losing your code. Written in Go
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
bat - A cat(1) clone with wings.
git-repo-manager - A git tool to manage worktrees and integrate with GitHub and GitLab