HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
simonthum
git-sync
Shell2016–2024
simonthum / git-sync

git-sync

Safe and simple one-script git synchronization

Developer ToolsSystems & Infrastructure
Explore on GitHubRead Hacker News discussions
3Distinct people
4Mentions
0Explicit recommenders
898GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Safe and simple one-script git synchronization

GitHub

Where it is used

No documented product use has been verified yet.

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, 12:54:37 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 year4 dated mentions

Observed mentions: 2016-04-30 19:15:25 UTC to 2024-07-28 20:56:24 UTC.

012016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC000
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110

What Hacker News says

4 sources
cidra_·Jul 28, 2024Submission

ASK HN: Some thoughts on a possible AST-aware org-mode three way merge driver

One thing I'm always craving for is a way to seamlessly sync my Org documents between my laptop, my smartphone and my tablet. Using git (along with some utilities like git-sync[0]) is decent, but when it comes to capturing a lot or heavily operating on a large agenda file, it's easy to incur in some conflicts that need manual intervention which kind of take away the smoothness from my plannings. I've noticed that many people do use git for syncing their notes and treat manual conflict handling simply as part of life. For some reasons I just can't bring myself to like it, but I also really would like to have full syncing capabilities on Org mode. I've seen that in 2012 some folks implemented a dedicated merge driver (org-merge-driver[1]) which only covers the basics but is aware of org syntax and operated on a per-headline basis, merging t
Read the rest
ags if needed and identifying changes from the name/id of the headline. I've been wondering if something like this could be re-implemented using org-mode's own parser (org-element). I've been reading a paper that describes a three way merge for XML documents (and generic hierarchical documents) without IDs being involved[2] and another paper that describes a way to merge ordered sequences that takes movements (even crossing ones), deletions and insertions into account[3]. Nothing bleeding edge and I wonder if something like this may stand on its own feet from a functional and performance perspective. Do you think something like this may be a good idea? Do you have some advice to give on this regard? Sorry for the quite abstract and quite fluff-y post, but this idea has been hanging in my head for too long. [0] https://github.com/simonthum/git-sync [1] https://orgmode.org/worg/org-contrib/gsoc2012/student-projects/git-merge-tool/manu… [2] A three-way merge for XML documents :: https://dl.acm.org/doi/10.1145/1030397.1030399 [3] A graph-based algorithm for three-way merging of ordered collections in EMF models :: https://www.sciencedirect.com/science/article/pii/S0167642315000532
6 points · Open discussion
WhatIsDukkha·Sep 25, 2019
Hmm what features would a git synced via - https://github.com/simonthum/git-sync #this gives low friction commits/pull/push Using https://github.com/rexim/org-cliplink #this gives nice looking links in your orgmode When added to orgmode it far past what a standalone bookmarks managerey thing does. ie - follow up to this github issue in 3 weeks with a bookmark in the TODO Ymmv of course.
In Show HN: Shiori v1.5 – Self hosted bookmarks manager, now with archival support

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.