-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adds "how we work" section across READMEs (#156)
* docs(README): adds "how we work" section * nit(README): reformulate warning * nit(README): change from warning to tip * docs(cli): adds "how we work" section in README * docs(base): adds "how we work" section in README * docs(connect): adds "how we work" section in README * docs(contractkit): adds "how we work" section in README * docs(cryptographic-utils): adds "how we work" section in README * docs(explorer): adds "how we work" section in README * docs(governance): adds "how we work" section in README * docs(keystores): adds "how we work" section in README * docs(network-utils): adds "how we work" section in README * docs(phone-utils): adds "how we work" section in README * docs(transaction-uri): adds "how we work" section in README * docs(utils): adds "how we work" section in README * docs(wallet-base): adds "how we work" section in README * docs(wallet-hsm): adds "how we work" section in README * docs(wallet-hsm-aws): adds "how we work" section in README * docs(wallet-hsm-azure): adds "how we work" section in README * docs(wallet-hsm-gcp): initializes new README with "how we work" section * docs(wallet-ledger): initializes new README with "how we work" section * docs(wallet-local): initializes new README with "how we work" section * docs(wallet-remote): initializes new README with "how we work" section * docs(wallet-rpc): initializes new README with "how we work" section * docs: adds auto-generated documentation
- Loading branch information
1 parent
ae51ca8
commit eeeba23
Showing
26 changed files
with
547 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,23 @@ | ||
|
||
|
||
# @celo/explorer | ||
|
||
Explorer depends on contractkit and connect. It provides some utility functions that make it easy to listen for new block and log information. | ||
|
||
## How we work | ||
|
||
We are a GitHub-first team, which means we have a strong preference for communicating via GitHub. | ||
Please use GitHub to: | ||
|
||
π [File a bug report](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π¬ [Ask a question](https://github.com/celo-org/developer-tooling/discussions) | ||
|
||
β¨ [Suggest a feature](httpsi//github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π§βπ» [Contribute!](/CONTRIBUTING.md) | ||
|
||
π [Report a security vulnerability](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
> [!TIP] | ||
> | ||
> Please avoid messaging us via Slack, Telegram, or email. We are more likely to respond to you on | ||
> GitHub than if you message us anywhere else. We actively monitor GitHub, and will get back to you shortly π |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,21 @@ | ||
# @celo/keystores | ||
|
||
## How we work | ||
|
||
# @celo/keystores | ||
We are a GitHub-first team, which means we have a strong preference for communicating via GitHub. | ||
Please use GitHub to: | ||
|
||
π [File a bug report](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π¬ [Ask a question](https://github.com/celo-org/developer-tooling/discussions) | ||
|
||
β¨ [Suggest a feature](httpsi//github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π§βπ» [Contribute!](/CONTRIBUTING.md) | ||
|
||
π [Report a security vulnerability](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
> [!TIP] | ||
> | ||
> Please avoid messaging us via Slack, Telegram, or email. We are more likely to respond to you on | ||
> GitHub than if you message us anywhere else. We actively monitor GitHub, and will get back to you shortly π |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,23 @@ | ||
|
||
# @celo/network-utils | ||
|
||
@celo/network-utils provides utilities for getting genesis block and static node information. | ||
|
||
## How we work | ||
|
||
We are a GitHub-first team, which means we have a strong preference for communicating via GitHub. | ||
Please use GitHub to: | ||
|
||
π [File a bug report](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π¬ [Ask a question](https://github.com/celo-org/developer-tooling/discussions) | ||
|
||
β¨ [Suggest a feature](httpsi//github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
π§βπ» [Contribute!](/CONTRIBUTING.md) | ||
|
||
π [Report a security vulnerability](https://github.com/celo-org/developer-tooling/issues/new/choose) | ||
|
||
> [!TIP] | ||
> | ||
> Please avoid messaging us via Slack, Telegram, or email. We are more likely to respond to you on | ||
> GitHub than if you message us anywhere else. We actively monitor GitHub, and will get back to you shortly π |
Oops, something went wrong.