NotesHub: changes inside a subfolder create empty Git commits

[techsemhype]

Hi Alex,

First of all, thank you for NotesHub. I've been using it for years and I really like the app, especially the Git-based approach and the fact that it works across iOS and Android.

I think I finally reproduced an old sync issue I had forgotten about.

My Git repository root is intentionally one level above my notes folder:

repo/
├── md/
│   └── notes.md
├── sh/
└── multiversox/

I connect this repository to NotesHub on iOS and can browse and open md/notes.md normally.

Reading/syncing from GitHub works perfectly.

The problem happens when editing md/notes.md in NotesHub:

1. Edit md/notes.md on iOS.
2. Save the note.
3. Force NotesHub sync.
4. NotesHub successfully creates and pushes a new commit to GitHub.
5. On the Mac, git pull receives that commit normally.
6. However, the commit contains no file changes and md/notes.md remains unchanged.

For example:

4b5aec8 create/update 'notes.md' file

but:

git show --name-status 4b5aec8

shows no modified file at all.

I reproduced it multiple times. Authentication, fetch, push and fast-forward all work correctly; only the actual note modification is missing from the commit.

My suspicion is that NotesHub is treating notes.md as being at the notebook/repository root instead of preserving its real Git path md/notes.md.

Would it be possible to support this repository layout, where Markdown notes live inside a subfolder of a larger Git repository?

I can provide additional logs or run a minimal reproduction repo if that helps.

Small additional finding that may help reproduce the issue:

I also tested the opposite direction: Mac → GitHub → NotesHub.

I edited md/notes.md on the Mac, committed/pushed it normally, and verified that origin/main contains the new text.

On the existing NotesHub notebook:

• iOS showed: An unhandled error occurred, please try again
• Android did not receive the remote change
• GitHub authentication itself remained active

Then I removed the notebook from NotesHub and added the exact same repository again (techsemhype/mac).

After re-adding it, the new text from md/notes.md appeared correctly on iOS.

So this does not seem to be an authentication problem. It looks more like the existing local notebook/clone state becomes inconsistent after external Git commits, and recreating the notebook forces a clean clone that works again.

This may be related to the subfolder/path issue described above.

Thanks!

[alex-titarenko]

Hi @techsemhype,

NotesHub supports markdown files to be located at any sub-folder level in the repo.
So I don't quite understand what is not working in your case.

Could you create a minimum reproduction repo and add me as a collaborator to the repo so I can try on my side?

[techsemhype]

Hi Alex, Thanks. I have a clearer reproduction now, and I think my original subfolder hypothesis may have been wrong. The interesting part is that the same repository currently works correctly in the opposite direction: Mac → GitHub → NotesHub works. Changes made to the markdown file on the Mac appear correctly in NotesHub on both iOS and Android. The remaining issue is NotesHub → GitHub. I edited the same markdown file separately on iPhone and Android and forced a sync on both. Only one new commit arrived on the remote: 82ec58b..c7b5d54 main -> origin/main Updating 82ec58b..c7b5d54 Fast-forward However, the commit is empty. I verified it directly on the GitHub web UI: commit c7b5d54 shows "0 files changed", and the file content in that commit is identical to the previous Mac-side version. Neither mobile edit is present. So authentication, remote fetch/push, branch tracking and Mac-side Git synchronization are all working. NotesHub is creating and pushing a new remote commit, but the commit contains no file changes — and one of the two mobile syncs apparently produced no commit at all. I'll create the minimal reproduction repo you requested and add you as a collaborator, so it's fully isolated from my real repository and tooling. Thanks again for looking into it. Em seg., 24 de ago. de 2026 às 00:37, Alex Titarenko < ***@***.***> escreveu:

…

Hi @techsemhype <https://github.com/techsemhype>, NotesHub supports markdown files to be located at any sub-folder level in the repo. So I don't quite understand what is not working in your case. Could you create a minimum reproduction repo and add me as a collaborator to the repo so I can try on my side? — Reply to this email directly, view it on GitHub <#96?email_source=notifications&email_token=BKGR2ZU2J77PU5BCMVJFPET5LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18129893>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKGR2ZVDS5SS5DWHYAPZULT5LOZ6VAVCNFSNUABIKJSXA33TNF2G64TZHM2TGMRTGU2TIMZYHNCGS43DOVZXG2LPNY5TCMBWGY3DIOJVUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BKGR2ZWRJ2BLODFIEOJEYWD5LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/BKGR2ZRIJNVDK3PRDHHYJX35LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[techsemhype]

One additional data point while I prepare the repro repo: This morning the existing "mac" notebook broke again on its own, on both iOS and Android at the same time ("An unhandled error occurred, please try again" on sync). GitHub authentication remains valid on both devices. The trigger seems consistent: it happens after the remote receives commits made outside NotesHub (from my Mac). Removing and re-adding the notebook fixes it every time, until the next external commit. So the pattern so far: after an external commit, the existing notebook state becomes inconsistent — syncs either fail with the error above, or produce an empty commit like c7b5d54. A fresh clone (re-adding the notebook) always works. I'll include steps to trigger this in the repro repo. [image: error.png] <img width="590" height="1278" alt="error" src="https://github.com/user-attachments/assets/41a355b0-815c-4c81-9f5c-36f26fdada67" /> Em seg., 24 de ago. de 2026 às 11:46, Daniel Bryan ***@***.***> escreveu:

…

Hi Alex, Thanks. I have a clearer reproduction now, and I think my original subfolder hypothesis may have been wrong. The interesting part is that the same repository currently works correctly in the opposite direction: Mac → GitHub → NotesHub works. Changes made to the markdown file on the Mac appear correctly in NotesHub on both iOS and Android. The remaining issue is NotesHub → GitHub. I edited the same markdown file separately on iPhone and Android and forced a sync on both. Only one new commit arrived on the remote: 82ec58b..c7b5d54 main -> origin/main Updating 82ec58b..c7b5d54 Fast-forward However, the commit is empty. I verified it directly on the GitHub web UI: commit c7b5d54 shows "0 files changed", and the file content in that commit is identical to the previous Mac-side version. Neither mobile edit is present. So authentication, remote fetch/push, branch tracking and Mac-side Git synchronization are all working. NotesHub is creating and pushing a new remote commit, but the commit contains no file changes — and one of the two mobile syncs apparently produced no commit at all. I'll create the minimal reproduction repo you requested and add you as a collaborator, so it's fully isolated from my real repository and tooling. Thanks again for looking into it. Em seg., 24 de ago. de 2026 às 00:37, Alex Titarenko < ***@***.***> escreveu: > Hi @techsemhype <https://github.com/techsemhype>, > > NotesHub supports markdown files to be located at any sub-folder level in > the repo. > So I don't quite understand what is not working in your case. > > Could you create a minimum reproduction repo and add me as a collaborator > to the repo so I can try on my side? > > — > Reply to this email directly, view it on GitHub > <#96?email_source=notifications&email_token=BKGR2ZU2J77PU5BCMVJFPET5LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18129893>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BKGR2ZVDS5SS5DWHYAPZULT5LOZ6VAVCNFSNUABIKJSXA33TNF2G64TZHM2TGMRTGU2TIMZYHNCGS43DOVZXG2LPNY5TCMBWGY3DIOJVUF3AE> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/BKGR2ZWRJ2BLODFIEOJEYWD5LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> > and Android > <https://github.com/notifications/mobile/android/BKGR2ZRIJNVDK3PRDHHYJX35LOZ6VA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGI4TQOJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. > Download it today! > You are receiving this because you were mentioned.Message ID: > ***@***.*** > com> >