Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Dolt | 14,938 | 2 | a day ago | 214 | May 19, 2022 | 292 | apache-2.0 | Go | ||
Dolt – Git for Data | ||||||||||
Waking Up | 8,405 | 4 months ago | 19 | gpl-3.0 | ||||||
计算机基础(计算机网络/操作系统/数据库/Git...)面试问题全面总结,包含详细的follow-up question以及答案;全部采用【问题+追问+答案】的形式,即拿即用,直击互联网大厂面试:rocket:;可用于模拟面试、面试前复习、短期内快速备战面试... | ||||||||||
Versionpress | 2,553 | 6 months ago | 232 | PHP | ||||||
Git-based version control for WordPress. Whoa! | ||||||||||
Irmin | 1,697 | 13 days ago | 2 | March 30, 2022 | 139 | isc | OCaml | |||
Irmin is a distributed database that follows the same design principles as Git | ||||||||||
Learn Devops | 1,097 | 2 days ago | 1 | HCL | ||||||
I am using this repository to document my devops journey. I follow the process of learning everything by tasks. Every task has an associated objective that encompasses an underlying concept. Concepts including CloudProviders, Containers, ContainersOrchestration, Databases, InfrastructureAsCode, Interview, VersionControl etc in progress | ||||||||||
Datakit | 999 | a year ago | 34 | apache-2.0 | OCaml | |||||
Connect processes into powerful data pipelines with a simple git-like filesystem interface | ||||||||||
Git Heat Map | 940 | 2 months ago | 2 | JavaScript | ||||||
Visualise a git repository by diff activity | ||||||||||
Gaskit | 927 | 9 years ago | 3 | other | JavaScript | |||||
a git-backed issue tracker | ||||||||||
Redwood | 749 | 2 | 4 months ago | 26 | April 18, 2021 | 111 | mit | Go | ||
A highly-configurable, distributed, realtime database that manages a state tree shared among many peers. | ||||||||||
Gitmodel | 542 | 7 | 1 | 3 years ago | 8 | September 30, 2012 | 9 | mit | Ruby | |
An ActiveModel-compliant persistence framework for Ruby that uses Git for versioning and remote syncing. |
Map showing the files in cpython that Guido van Rossum changed the most;
full SVG image available in repo
A version of this program is now available for use at heatmap.jonathanforsythe.co.uk
python generate_db.py {path_to_repo_dir}
flask
from pippython app.py
or flask run
(flask run --host=<ip>
to run on that ip address, with 0.0.0.0
being used for all addresses on that machine)127.0.0.1:5000
%
acting as a wildcardThis project consists of two parts:
Scans through an entire git history using git log
, and creates a database using three tables:
Using these we can keep track of which files/commits changed the repository the most, which in itself can provide useful insight
Taking the database above, uses an SQL query to generate a JSON object with the following structure:
directory:
"name": <Directory name>
"val": <Sum of sizes of children>
"children": [<directory or file>, ...]
file:
"name": <File name>
"val": <Total number of line changes for this file over all commits>
then uses this to generate an inline svg image representing a treemap of the file system, with the size of each rectangle being the val
described above.
Then generates a second JSON object in a similar manner to above, but filtering for the things we want (only certain emails, date ranges, etc), then uses this to highlight the rectangles in varying intensity based on the val
s returned eg highlighting the files changed most by a certain author.
These speeds were attained on my personal computer.
Repo | Number of commits | Git log time | Git log size | Database time | Database size | Total time |
---|---|---|---|---|---|---|
linux | 1,154,884 | 60 minutes | 444MB | 462.618 seconds | 733MB | 68 minutes |
cpython | 115,874 | 4.6 minutes | 44.6MB | 36.607 seconds | 74.3MB | 5.2 minutes |
Time taken seems to scale linearly, going through approximately 300 commits/second, or requiring 0.0033 seconds/commit. Database size also scales linearly, with approximately 2600 commits/MB, or requiring 384 B/commit.
For this test I filtered each repo by its most prominent authors:
Repo | Author filter | Drawing treemap time | Highlighting treemap time |
---|---|---|---|
linux | [email protected] | 19.7 s | 54.3 s |
cpython | [email protected] | 842 ms | 1238 ms |
These times are with minimum size drawn = 0
, on very large repositories, so the performance is not completely unreasonable. This does not include the time for the browser to actually render the svg, which can take longer.
Currently the only submodule changes that can be seen are the top level commit pointer changes. In the future would like to recursively explore submodules and add their files to the database.
Currently done using git log which can take a very long time for large repos. Will look into any other ways of getting needed information on files.
Currently the user can submit only a single query for the highlighting. Ideally they could have a separate filter dictating which boxes to draw in the first place, and possibly multiple filters that could result in multiple colour highlighting on the same image.