-
Notifications
You must be signed in to change notification settings - Fork 146
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* sync changes from coreth-0.11.6 * remove diff patch * revert format changes * nits (#441)
- Loading branch information
Showing
28 changed files
with
1,650 additions
and
170 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,35 +1,34 @@ | ||
# Contributing | ||
|
||
Thank you for considering to help out with the source code! We welcome | ||
contributions from anyone on the internet, and are grateful for even the | ||
Thank you for considering to help out with the source code! We welcome | ||
contributions from anyone on the internet, and are grateful for even the | ||
smallest of fixes! | ||
|
||
If you'd like to contribute to coreth, please fork, fix, commit and send a | ||
If you'd like to contribute to subnet-evm, please fork, fix, commit and send a | ||
pull request for the maintainers to review and merge into the main code base. If | ||
you wish to submit more complex changes though, please check up with the core | ||
devs first on [Discord](https://chat.avalabs.org) to | ||
ensure those changes are in line with the general philosophy of the project | ||
you wish to submit more complex changes though, please check up with the core | ||
devs first on [Discord](https://chat.avalabs.org) to | ||
ensure those changes are in line with the general philosophy of the project | ||
and/or get some early feedback which can make both your efforts much lighter as | ||
well as our review and merge procedures quick and simple. | ||
|
||
## Coding guidelines | ||
|
||
Please make sure your contributions adhere to our coding guidelines: | ||
|
||
* Code must adhere to the official Go | ||
[formatting](https://golang.org/doc/effective_go.html#formatting) guidelines | ||
(i.e. uses [gofmt](https://golang.org/cmd/gofmt/)). | ||
* Code must be documented adhering to the official Go | ||
[commentary](https://golang.org/doc/effective_go.html#commentary) guidelines. | ||
* Pull requests need to be based on and opened against the `master` branch. | ||
* Pull reuqests should include a detailed description | ||
* Commits are required to be signed. See [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) | ||
for information on signing commits. | ||
* Commit messages should be prefixed with the package(s) they modify. | ||
* E.g. "eth, rpc: make trace configs optional" | ||
- Code must adhere to the official Go | ||
[formatting](https://golang.org/doc/effective_go.html#formatting) guidelines | ||
(i.e. uses [gofmt](https://golang.org/cmd/gofmt/)). | ||
- Code must be documented adhering to the official Go | ||
[commentary](https://golang.org/doc/effective_go.html#commentary) guidelines. | ||
- Pull requests need to be based on and opened against the `master` branch. | ||
- Pull reuqests should include a detailed description | ||
- Commits are required to be signed. See [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) | ||
for information on signing commits. | ||
- Commit messages should be prefixed with the package(s) they modify. | ||
- E.g. "eth, rpc: make trace configs optional" | ||
|
||
## Can I have feature X | ||
|
||
Before you submit a feature request, please check and make sure that it isn't | ||
Before you submit a feature request, please check and make sure that it isn't | ||
possible through some other means. | ||
|
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
Oops, something went wrong.