Muir Manders

We are on the verge of major doc updates. Properly documenting "automation mode" is in the plans.

> translated into PR comments on GitHub that are posted after the force-push I think that is the intention of the `sl pr submit --message "..."` option you found, but...

Seems reasonable to support pushing to arbitrary refs. We could add detection for "refs/" prefix and, if present, use verbatim, but that would preclude having a branch named "refs/foo". @quark-zju...

I cut out some outdated content in ea975582515db81c6ccddf986630a568ac4d613f. I think it's mostly okay now, except the last part isn't true in all cases for git repos. @lf- Are you satisfied...

We are planning to rework the Sapling open source build process. We will keep the offline build support in mind. /cc @bigfootjon

Is someone actively working on this? I've been playing around with different buffer pool strategies, but don't want to look too much more if I'm just duplicating work. I've been...

There is notable garbage produced outside of proto marshaling in the http2 transport, so I was hoping to address that too. I was looking at more generic []byte buffer reuse...

My thought was instead of returning the buffer to the codec, return the buffer to the generic buffer pool instead. Then anyone can pull a buffer from the pool, and...

Another way to fix this might be to make `derivableTypes` _not_ try "deriving" a pointer from `interface`, `chan`, etc. types that already have pointer semantics. In the example, `derivableTypes` says...

> helm/ivy support that, no? You can do it with ivy using a separate package `ivy-xref` and then `ivy-occur` to pop it out into a full buffer you can iterate...