Currently checking for issues and patches is a manual action. It requires the user to call rad inbox and spot the new items. Missing new items is quite easy when one doesn’t issue the command frequently.

Users should be able to be notified of new items when the radicle node fetches them. One way of doing so is by allowing the user to configure hooks.

Proposal

Hooks to certain lifecycle events should be made available. The hooks should be configurable and allow calling a script upon being triggered.

Possible hooks

inbox:issue:opened
inbox:issue:updated
inbox:issue:closed
inbox:patch:created
inbox:patch:updated
inbox:patch:applied
inbox:patch:rejected

fintohaps commented 1 year ago

Thanks for creating an issue for this :) It’s actually something that’s been our radar and I’ve started put some things in place to get there.

So, the node already has an event stream that other applications can listen to – either via the CLI or using the library directly.

One part of the implementation is being able to get a stream of the COB operations that occurred in a given range (see here). The next part of the process would be to hook these components into the event stream, when the node fetches, so that they can be emitted.

The application can then see exactly what operations were performed and by whom.