Signed-off-by: oppiliappan <me@oppi.li>

similar to jetstream consumer, we now ingest events from every known
knot.

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: oppiliappan <me@oppi.li>

tracks commit per user by day

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: oppiliappan <me@oppi.li>

consumers can configure a cursor-store, where cursors of individual
event sources are stored. the module provides an in-memory store and a
redis-backed store.

Signed-off-by: oppiliappan <me@oppi.li>

- EventSource: a knot's identity (its hostname currently)
- Message: message struct that follows the event structure to
deserialize just rkey and nsid upfront, this could allow consumers to
filter by nsid or configure cursor ranges to listen to

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: oppiliappan <me@oppi.li>

initial commit does not have a parent commit and should be excluded from
the signature check.

Signed-off-by: oppiliappan <me@oppi.li>

this was incorrectly adding the current pull into the formatpatch twice.

Signed-off-by: oppiliappan <me@oppi.li>

Signed-off-by: oppiliappan <me@oppi.li>

takes a yaml based workflow and compiles it down to a
sh.tangled.pipeline object, after performing some basic analysis.

Signed-off-by: oppiliappan <me@oppi.li>

in order to work around the limitations of not having github actions'
marketplace, this approach opts to use nixpkgs as a source for packages.
alternate registries can be specified too, these are expected to be nix
flakes that expose packages.

this takes a page out of replit's approach to supplying packages to
their devshells, however, instead of using nix syntax, we use only a
flake + package combo, and the compiler will simply convert this into a
step like so:

nix profile install flake#package

Signed-off-by: oppiliappan <me@oppi.li>