-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs:Building_a_network_skeleton.md cleanups #12079
Conversation
All checks have passed |
Go-State-Types Checklist updates
…ead of 3 or more "x"'s in some cases. Adjusted ToC.
Go-State-Types Checklist updates
…ead of 3 or more "x"'s in some cases. Adjusted ToC.
Go-State-Types Checklist updates
…ead of 3 or more "x"'s in some cases. Adjusted ToC.
e97641c
to
35b0155
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rebased the PR on master to include only the actual diff in this PR, excluding all other merge commits. Hope that's okay!
The changes looks good to me, and I like the simplification in the step where you need to change all references from vX to v(X+1) in Go-State-Types! Merge at will.
Doh - yes - thanks for fixing. My bad. I should have caught that. My git foo is rusty. I was trying to do this in VS Code. I'll sync up with you offline in the way you do this so I don't repeat that mistake. Thanks again for the help. |
Proposed Changes
Making some updates/changes while reading through Building_a_network_skeleton.md
Additional Info
Go-State-Types Checklist updates
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, depsIf the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.New features have usage guidelines and / or documentation updates inLotus DocumentationDiscussion TutorialsTests exist for new functionality or change in behavior