I noticed an error in the Hedera docs and decided to try to fix them and contribute to the community. The process looked like this: First I forked the official docs and created my copy. Then in VS Code, I cloned my fork. From there I went into the file and fixed the errors. After checking the 'remote' and 'branch' and making sure they're proper. I committed the changes. The hedera docs require something called Developer Certificate of Origin, which requires the commit to use the --signoff flag to add credentials to the commit message. From there, the changes were pushed onto my repository. Lastly, I went back to Hedera Docs GitHub page and submitted a new pull request. All the while I tried to make sure my commit message and PR description were descriptive and well written.
Subscribe to:
Post Comments (Atom)
190: Sablier
The CodeHawks platform has an upcoming audit on the Sablier protocol, so I decided to read through the docs and familiarize myself with the...
-
The CodeHawks platform has an upcoming audit on the Sablier protocol, so I decided to read through the docs and familiarize myself with the...
-
The ZKasino project recently exit scammed over 33 million dollars worth of Ethereum. he recent debacle surrounding ZKasino offers valuable...
-
In addition to its native SDK, Hedera also supports smart contracts in a platform compatible with the Ethereum Virtual Machine. This allows ...
No comments:
Post a Comment