Replying to Avatar average_bitcoiner

For a source control merge request context client, you really just need to track the remote URL for the main repo and where to find the desired merge branch. Everything else can be bolted on NIP-10 style.

What about issue tracking? Feels like a kind for issues is appropriate but there should be customization for how they’re tracked. Not everyone follows the same pattern.
Avatar
average_bitcoiner 2y ago

Someone mentioned git-bug to me before and maybe that’s right, but idk if messing with devs git workflows is right. If you’re a dev, would you adopt a git-bug approach if it integrated with nostr?

Reply to this note

Please Login to reply.

Discussion

Avatar
average_bitcoiner 2y ago

I should read this thread, and maybe you too.

https://github.com/Byron/gitoxide/discussions/52