Nate Gaylinn on Nostr: I'm working on a few related #Python #programming projects, which will have a few ...
I'm working on a few related #Python #programming projects, which will have a few libraries shared between them. Ideally, I'd like one #git repo for each project and for each of the shared libraries, without too much hassle for me while I'm developing them. I'm relatively new to git, though, so I'm not sure what the best way to do this is! What do you usually do in this situation? Seen anybody do this particularly well / badly?
Published at
2024-03-02 15:51:41Event JSON
{
"id": "5eb71df87ef9df3c96a725bd78bce42b6e412f295a29b36cb90e3019394e4169",
"pubkey": "7170b99dada6350d3bf615ce8af39d6c8326bd8504a96f97b107ea56b3a25748",
"created_at": 1709394701,
"kind": 1,
"tags": [
[
"t",
"python"
],
[
"t",
"programming"
],
[
"t",
"git"
],
[
"proxy",
"https://tech.lgbt/users/ngaylinn/statuses/112026891188369214",
"activitypub"
]
],
"content": "I'm working on a few related #Python #programming projects, which will have a few libraries shared between them. Ideally, I'd like one #git repo for each project and for each of the shared libraries, without too much hassle for me while I'm developing them. I'm relatively new to git, though, so I'm not sure what the best way to do this is! What do you usually do in this situation? Seen anybody do this particularly well / badly?",
"sig": "186b3c8722d43abdd6b3243afefc322d7220ac6e78be6b3ba40ec04060a30dbef4abf51070308d141dd73cc797872cb81da771f5ed625691ac9f313691f9ae5e"
}
