'Notes' is now 'trilium' - responding to the change

[maphew]

Great news! Zadam's trilium repository is now under the TriliumNext organisation's umbrella.

• https://github.com/TriliumNext/Notes/discussions/2190

There's some unavoidable short term churn until the migration is complete. I started this thread to collect info and tips on how to handle the rename while things settle out.

• Issues from TriliumNext/Notes have been migrated to TriliumNext/trilium. You don't need to do anything, for the most part Github will just redirect from old to new for any links. However:

  • Notifications - clicking on a Github notifcation link for .../Notes/27 will redirect to ../trilium/27, which is a completely different issue, resulting in a very confusing experience. Easiest thing to do is clear all the notifications. If needed, search for the issue title to get the new number.

• Discussions: Use https://github.com/orgs/TriliumNext/discussions, not the archived github.com/orgs/TriliumNext/Notes/discussions (the latter is nested under the now retired repo, while the former is for everything).

Edit: removed mistaken advice about updating a local fork to new upstream. It's not as straightforward as I made it seem. will re-edit this post after more testing

[maphew]

I didn't figure out how to cleanly point an existing clone with personal branches from TriliumNext/Notes to TriliumNext/Trilium. (My git knowledge is basic.) In the end I decided it was simpler, and certainly less mental gymnastics, to simply clone a fresh copy of Trilium and then manually copy over or patch the changes I'm still interested in working on. The branch history is not interesting enough to try to maintain.

[eliandoran]

@maphew , generally you can add a new remote as such:

git remote add new /path/to/newly/cloned/repo

Since both projects are related, you can share branches together. But doing it the manual way also works, ofc.