Oddbean new post about | logout
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 I think I have a problem because I have two different repos with the same name, but different source repos.

One is a fork of the other
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 Isn't it confusing to maintain two different repos with the same name?
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 yes 😂

Never occured to me to rename them, since I've never maintained the source and the fork, before. Used to only work with branches on the source repo.

I should go rename all my forks, so that I can identify them.
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 What are the purposes of the forks? Do they differ signifcantly? Why not have them as branches of the same repo?
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 We're using the same as branches, with each dev having a fork that they're working on and then making a PR to the source repo for merges.

Just looks neater in the source.
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag 
 Each dev would use the source repo to get the lastest changes. Then use `ngit send` to create proposal (PR equivalent) when they ready to share what they are working on. They can update the proposal with `ngit push` or after a rebase they can use `ngit push --force`. `git merge`  can be used for merging into the master branch to be pushed to the source repo.
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 Okay, looks much better. 😅  I was so confused!
Just prefacing my forks all with "sw_".

https://gitworkshop.dev/repo/sw_gitcitadel
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag +1 
 It only makes sense to have a nostr repo event for a distinct repository that you would want to receive proposals for or raise issues against. This typically wouldn't be one per developer.
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 Okay, so then it would only need to be the source repos and not my forks. That makes sense.
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 I'm going to keep testing on my fork, tho, to keep the source one neat.

Let me go try to send something again and get you the output.
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 If a user-npub wrote me on Nostr with a bug, how do I turn that into an issue? With some sort of a quote or reply?
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag +1 
 Hey, nostr:nprofile1qyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6xk8zw9  that markdown looks very pretty. I like that. Displays on GitWorkshop better than on GitHub.
▲ ▼
DanConwayDev | 7 months ago (raw) | root | parent | reply | flag +1 
 Thanks.
▲ ▼
Laeserin | 7 months ago (raw) | root | parent | reply | flag 
 The table, especially. Neat and streamlined.
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 This is what I got on the command:

logged in as SilberWitch
 ✔ 1 events   wss://nostr.sovbit.host/ 
 ✔ 1 events   wss://theforest.nostr1.com/                                       posting 1 patch with a covering letter...
 ✔  [my-relay] [repo-relay] wss://nostr.sovbit.host/ 
 ✔  [my-relay] [repo-relay] wss://theforest.nostr1.com/ 
 ✔  [default] wss://relay.damus.io 
 ✔  [default] wss://nos.lol 
 ✔  [default] wss://relay.nostr.band 
 ✘  [default] wss://relay.f7z.io error: recv message response timeout
▲ ▼
Silberengel | 7 months ago (raw) | root | parent | reply | flag 
 I just realized that I accidentally named the repo "SilberWitch" instead of gitcitadel. 🤦‍♀️

How can I fix that?