ANanonova·Jun 10, 2026
Grit was the name of a _Ruby_ implementation of git way back when: https://github.com/mojombo/grit/. I believe it's actually what GitHub was built on then.
In Grit: Rewriting Git in Rust with agentsmojombo
grit
Ruby2010–2026
mojombo / grit
grit
**Grit is no longer maintained. Check out libgit2/rugged.** Grit gives you object oriented read/write access to Git repositories via Ruby.
13Distinct people
13Mentions
0Explicit recommenders
2KGitHub stars
What to know before exploring
What it is
**Grit is no longer maintained. Check out libgit2/rugged.** Grit gives you object oriented read/write access to Git repositories via Ruby.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year13 dated mentions
Observed mentions: 2010-08-31 20:12:32 UTC to 2026-06-10 00:16:27 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2010 | 2010-01-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
13 sourcesAnd the first commit: https://github.com/mojombo/grit/commit/634396b2f541a9f2d58b0...
In Congratulations on creating the one billionth repository on GitHubWhile we are doing cool GitHub repo IDs, the first is here:
https://api.github.com/repositories/1
https://github.com/mojombo/grit
In Congratulations on creating the one billionth repository on GitHubGrit – the first repository on GitHub
2 points · Open discussionThe very first GitHub commit, committed 10 days before the author joined GitHub
3 points · Open discussionheh, what at the odds: two libs that give you object-oriented access to git repos both coincidentally named the exact same thing:
python: github.com/rsgalloway/grit
ruby: github.com/mojombo/grit
In Self-hosted Git ServerGrit - Object oriented read/write access to Git repositories via Ruby
2 points · Open discussionAre you referencing Grit? https://github.com/mojombo/grit
In Why the use of GPL is decliningWe don't have immediate plans for other VCSs.
None of the people who built Barkeep use other VCSs on a regular basis, and we initially built it around our own needs.
Right now our code is tightly tied to grit (https://github.com/mojombo/grit/). We plan on moving off of grit at some point (perhaps to libgit2/rugged), and that would be a good time to abstract our VCS layer, opening up the possibility for use with other systems besides git.
In Show HN: Barkeep, the friendly code review systemI have written some scripts for code analysis needs via git/grep/awk/ruby. code metrics, top committers, frequently committed files, duplications etc
you can find some interesting question with solutions
http://stackoverflow.com/questions/tagged/git?sort=votes&...
if you need low level access https://github.com/mojombo/grit
could you elaborate, what your expectations are, I can give pointers or share some of my code
In Ask HN: Any good git parser/data analysis tools out there?"It doesn't have a library for efficient in-process access"
https://github.com/mojombo/grit
In Git as a NoSQL datastoreHello world.
I'm at kind of a crossroads: I want to make a site that will feature a web based editor for text files in some markup languages aimed for non-developer users, but I want to offer them the ability to track changes to those files and maybe even "fork" and "merge" other documents/document-clusters; again, all via a web interface. Basically, you could say that it's like a web-based github for non-devs.
I could use a key-value store like couchdb or cassandra to store diffs between times when something is saved to show histories and do merges with one of the strategies git uses; and maybe in the future let users use a desktop app and thus clone/push/pull changes like a regular git hosting site. Again, in a skimmed non-dev approach to git.
For the record, this talk has practically convinced me of using git http://www.techscreencast.
Read the rest
com/language/ruby/using-git-in-ruby-applications---scott-chacon-/1431 because I realize that it might seem overkill at first but I don't want to end up reinventing git. But a little n00b voice in my head still screams overkill.
So, hackerworld, what's your take on this? I mean, I could just do something with the [ruby](http://github.com/mojombo/grit)/(python)[http://gitorious.org/git-python] interfaces to git and something like gitosis, or create my own subset of file history management like said above; what would be the wisest choice?
While the site isn't open-source, they have open-sourced a ton of code. Just to name a few:
http://github.com/github
http://github.com/defunkt/resque
http://github.com/mojombo/jekyll
http://github.com/mojombo/god
http://github.com/mojombo/bert
http://github.com/mojombo/grit
In GitHub launches Pull Requests 2.0