|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Git Time Machine||1,128||4 years ago||44||mit||CoffeeScript|
|Atom package that allows you to travel back in commit history|
|Gtm||795||4 years ago||25||August 02, 2019||42||mit||Go|
|Simple, seamless, lightweight time tracking for Git|
|Glass||594||3 years ago||8||July 14, 2015||32||mpl-2.0||Go|
|Automated time tracking for Git repositories. [DEPRECATED]|
|Git Punchcard Plot||156||2 years ago||5||Python|
|a tool to visualize the time distribution of commits|
|Tracklater||115||2 months ago||7||March 12, 2021||3||mit||Python|
|TrackLater helps you track time after-the-fact by combining clues and showing your day on a simple timeline view.|
|🦊🕘 A crossplatform menubar/taskbar application for GitLabs time tracking feature. Currently in BETA!|
|Git_time_extractor||95||6||8 years ago||6||May 21, 2015||7||Ruby|
|Analyzes Git repository commit logs to compute developer working hours, weekly activity, and to detect death marches in software development.|
|Gitpaid||63||12 years ago||Shell|
|The programmer's time tracker|
|Clockout||63||8 years ago||3||mit||Ruby|
|Log your hours worked using Git|
|Ia.bak||61||3 years ago||15||gpl-3.0||Shell|
|We back up a lot of stuff from around the web; now it's time to back up the Internet Archive, just in case.|
Client scripts for http://archiveteam.org/index.php?title=INTERNETARCHIVE.BAK/git-annex_implementation
You can use git-annex commands by hand, if you prefer, but the
script automates several things for you.
Clone this git repository to somewhere that has a lot of disk space,
and run the
iabak script to get started.
You can stop running it once it's downloaded enough. Just hit ctrl-C at any time.
This script has been tested on:
To be sure that your backup still exists and is still in good shape,
you shoud periodically run either
both. Either of these will check back in and verify that your repo
exists. The difference is that
iabak-cronjob avoids downloading any
more data from the IA, avoids verifying the checksums of the files you
are storing, and logs to
We recommend setting up a cron job that runs one of these at least once per week, so we can notice when repositories go missing or develop problems.
For example, to run it at 10:30am on Mondays, put this in crontab:
30 10 * * 1 /path/to/IA.BAK/iabak-cronjob
install-fsck-service installs a systemd timer or cron job that will run
iabak-cronjob once a day. This is now set up automatically the first time
iabak is run.
iabak will check out one shard of the IA at a time. Once it
finishes the current shard, if you have more disk space available, it will
find and check out another shard.
To manually check out a particular shard, you can run the
checkoutshard script, passing it the name of a shard, such as "shard3".
repolist file for a list of shards and their status.
Once you have multiple shards checked out, the next time you run
it will process all them.
You can touch these files in the IA.BAK directory to control
NOSHUFPrevents shuffling files before downloading.
iabakfrom checking out additional shards as existing shards complete.
Also, these files in the IA.BAK directory can have values written to them to tune its behavior.
Options passed to
git annex get.
This is useful to enable concurrent downloads of multiple files.
For example "-J10" for concurrent downloads.
Limits how much time is spent verifying checksums of
files in your backup. The default is "5h", which means
it will spend up to 5 hours per shard per run of
Feel free to set this to a smaller time limit like "1h" or "30m".
iabak-cronjob does not perform these expensive fscks.)
The goal is to verify the checksum of each file in your backup once per month. If it's interrupted by this time limit, or just by your ctrl-c, it will pick up next time where it left off. Once it's verified all files, it will avoid doing any more checksumming until the next month.
So you want to back up part of the IA, but don't want this to take over your whole disk or internet pipe? Here's some tuning options you can use.. Run these commands in git repos like IA.BAK/shard1, IA.BAK/shard2, etc.
git config annex.diskreserve 200GB
This will prevent git-annex from using up the last 200gb of your disk.
Adjust to suit. This is prompted for the first time you run
iabak, and it
is automatically propagated to each new shard.
git config annex.web-options --limit-rate=200k
This will limit wget/curl to downloading at 200 kb/s. Adjust to suit.
Note that if concurrent downloads are enabled, each download thread will use up to this rate limit.
If you cloned shard1 by hand before, here's how to convert to managing it with iabak.
Can I run this on BSD?
Not without some serious work. You'll need /bin/bash, GNU awk, and possibly other things I can't think of off the top of my head. Join the IRC channel and chat with other BSD users; they may have more up-to-date information.
Can I store the backups on an NFS or SMB filesystem?
Kinda. If you're using SMB then you're on your own (but do send us a pull request). If you're using NFS then you'll have to install git-annex manually (as the default install tarball uses symlinks), and you'll have to add "-c annex.sshcaching=false" to the ANNEXGETOPTS file so that git-annex doesn't try to create unix sockets on your NFS filesystem.
I keep seeing this error message from git-annex: "Unable to access these remotes: web"; what do I do?
This indicates that a file used to exist on archive.org but has since been hidden for one reason or another. The message will also list which git remotes are believed to contain the file; if remotes other than the web remote are listed then you could contact that user and arrange for access to the file. The best way to do this is to set up mutual SSH access.
What do I do when git-annex tells me "verification of content failed"?
This means that git-annex tried to verify the content of a file it has downloaded, but failed to do so. Most likely the file has changed since we first added it to the shard. This is most common with torrent files and the *_meta.xml files.