Steve Loeppky
Steve Loeppky
@ameeetgaikwad : just checking in on how this is going.
This is how I'm thinking to structure the conversation (with my proposal from what I know): Usecase | merge commits | squash merging | rebase merging | note -- |...
> The main reason I find myself reaching for squash merging these days is to fix up people's commit summaries. If someone has a nice PR title but sloppy commit...
Thanks all for the feedback. This makes sense. Unless someone says otherwise, I think the next step is for me to draft a PR to CONTRIBUTING and/or RELEASE_FLOW with this...
There's been lots of useful feedback here. I haven't incorporated it into a drafted doc. This is what I want to cover/do next week: Things I want to get documented:...
@rvagg : 1. Is the next step here to get @ZenGround0 to review? If so, he will probably need a Slack ping. 2. Is there a certain lotus release you...
@rjan90 : I did some updates to the template in the issue description. They were mostly cosmetic, but the key callouts were: 1. Capturing offline with and without pre-migration cache....
2024-09-04 update: @rvagg is active on this. He has generated a JS/TS client from an IPLD schema for the Lotus Common Node API and ETH RPC apis. He is calling...
Input welcome, but this is the kind of experience I would like to see from "tooling" ``` Here are the set of PRs that are in master that aren't in...
Thanks @rvagg for the NodeJS example. This was interesting to read. I'm trying to think about what proposal to make based on where we are today, the resources we have...