👋 Hello there! Welcome. Please follow the steps below to tell us about your contribution.
Please explain the intent of your Pull Request.
🐛 Are you fixing a bug?
📝 Are you updating documentation?
💻 Are you changing functionality?
Remember to state clearly and in detail, leaving no room for confusion about the intent of your Pull Request
Template
Description of the Change
We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
Verification Process
What process did you follow to verify that your change has the desired effects?
How did you verify that all new functionality works as expected?
How did you verify that all changed functionality works as expected?
How did you verify that the change has not introduced any regressions?
Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
Release Notes
Please describe the changes in a single line that explains this improvement in
terms that a user can understand.
If this change is not user-facing or notable enough to be included in release notes
you may use the strings "Not applicable" or "N/A" here.
Review
Pull Requests must have the sign-off of two other developers and at least one of these must be an IDX Broker team member.
Pull Requests
👋 Hello there! Welcome. Please follow the steps below to tell us about your contribution.
Please explain the intent of your Pull Request.
🐛 Are you fixing a bug?
📝 Are you updating documentation?
💻 Are you changing functionality?
Remember to state clearly and in detail, leaving no room for confusion about the intent of your Pull Request
Template
Description of the Change
We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts.
Verification Process
What process did you follow to verify that your change has the desired effects?
Describe the actions you performed (including buttons you clicked, text you typed, commands you ran, etc.), and describe the results you observed.
Release Notes
Please describe the changes in a single line that explains this improvement in terms that a user can understand.
If this change is not user-facing or notable enough to be included in release notes you may use the strings "Not applicable" or "N/A" here.
Review
Pull Requests must have the sign-off of two other developers and at least one of these must be an IDX Broker team member.