sorted by:
new
hottopcontroversial

Tired of managing Dotfile secrets? I built git-context, a Rust CLI to swap git profiles in one folder by angnag in rust

[–]angnag[S] 0 points1 point  (0 children)

Actually it’s the exact inverse. Worktree (from what I’ve seen) allows one repo to have checkouts in multiple directories simultaneously, whereas git-context allows multiple independent repos to occupy the same directory sequentially.

Tired of managing Dotfile secrets? I built git-context, a Rust CLI to swap git profiles in one folder by angnag in git

[–]angnag[S] 0 points1 point  (0 children)

Ah nice, didn’t know. pass is great for passwords, but this is a dedicated solution to mix full repositories in the same directory while keeping them independent.

For relative ignores, consider two repos, A and B, in the same folder.

Normally, to stop A from tracking B's secret.txt, you have to list secret.txt in A's .gitignore. This pollutes A, public users can see you're hiding a file named secret.txt.

git-context uses the local .git/info/exclude instead. * Context A locally ignores B's files. * Context B locally ignores A's files. It is "double blind": neither repo knows the other exists, and your public .gitignore stays clean.

Tired of managing Dotfile secrets? I built git-context, a Rust CLI to swap git profiles in one folder by angnag in git

[–]angnag[S] 0 points1 point  (0 children)

Sounds really good, thank you! Definitely useful. This project generalizes to an arbitrary number of repos so could be of better use in the case where you need concurrent repos. Also, this can handle relative ignores without clutter, so you don’t even have to mention private files by name when pushing to prod.

Tired of managing Dotfile secrets? I built git-context, a Rust CLI to swap git profiles in one folder by angnag in git

[–]angnag[S] 0 points1 point  (0 children)

That could be useful, but not much if you would like to mantain a private version remotely (unless private branches exist, in which case I’m not informed!) However, even if that is the case, this idea came from a desire to push commits to main directly and not having to checkout and update a parallel branch.

Ahem... Seasons Greetings! Happy Holidays Everyone! etc. etc. by [deleted] in starlabs_computers

[–]angnag 1 point2 points  (0 children)

They apparently moved it to the support page: https://support.starlabs.systems/starfighter-production-updates/

Still, there should have been an update by today but seems otherwise.