mirror of https://github.com/hyperledger/besu
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
61 lines
2.4 KiB
61 lines
2.4 KiB
<!-- Thanks for sending a pull request! Here are some tips for you:
|
|
1. If this is your first time, read our contributor guidelines
|
|
https://github.com/PegaSysEng/pantheon/blob/master/CONTRIBUTING.md#your-first-code-contribution
|
|
2. Label the PR appropriately how to mark it:
|
|
https://github.com/PegaSysEng/pantheon/blob/master/CONTRIBUTING.md#pull-request-labels
|
|
-->
|
|
|
|
# PR Details
|
|
|
|
<!--- Provide a general summary of your changes in the Title above -->
|
|
|
|
## Description
|
|
|
|
<!--- Describe your changes in detail -->
|
|
|
|
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
|
|
Fixes #
|
|
|
|
## Related Issue
|
|
|
|
<!--- This project only accepts pull requests related to open issues -->
|
|
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
|
|
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
|
|
<!--- Please link to the issue here: -->
|
|
|
|
## Motivation and Context
|
|
|
|
<!--- Why is this change required? What problem does it solve? -->
|
|
|
|
|
|
## Types of changes
|
|
|
|
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
|
|
|
|
- [ ] Docs change / refactoring / dependency upgrade
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
|
|
|
|
**Special notes for your reviewer**:
|
|
|
|
## Release note
|
|
<!-- Write your release note:
|
|
1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
|
|
2. If no release note is required, just write "NONE".
|
|
-->
|
|
```release-note
|
|
|
|
```
|
|
|
|
## Prerequisites:
|
|
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
|
|
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
|
|
- [ ] I have read the **CONTRIBUTING.md** document.
|
|
- [ ] This code follows the style guidelines of this project
|
|
- [ ] I have performed a self-review of my own code
|
|
- [ ] I have commented my code, particularly in hard-to-understand areas
|
|
- [ ] I have made corresponding changes to the documentation
|
|
- [ ] My changes generate no new warnings
|
|
- [ ] I have added appropriate tests that prove my change is effective
|
|
- [ ] New and existing tests pass locally with my changes
|
|
|