-
Notifications
You must be signed in to change notification settings - Fork 127
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into gkiko10/JOBS-19305
- Loading branch information
Showing
61 changed files
with
1,968 additions
and
1,640 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 +1 @@ | ||
cf9c61453990df0f9453670f2fe68e1b128647a2 | ||
5285ce76f81314f342c1702d5c2ad4ef42488781 |
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,12 +1,28 @@ | ||
## Changes | ||
<!-- Summary of your changes that are easy to understand --> | ||
## What changes are proposed in this pull request? | ||
|
||
## Tests | ||
<!-- | ||
How is this tested? Please see the checklist below and also describe any other relevant tests | ||
--> | ||
Provide the readers and reviewers with the information they need to understand | ||
this PR in a comprehensive manner. | ||
|
||
- [ ] `make test` run locally | ||
- [ ] `make fmt` applied | ||
- [ ] relevant integration tests applied | ||
Specifically, try to answer the two following questions: | ||
|
||
- **WHAT** changes are being made in the PR? This should be a summary of the | ||
major changes to allow the reader to quickly understand the PR without having | ||
to look at the code. | ||
- **WHY** are these changes needed? This should provide the context that the | ||
reader might be missing. For example, were there any decisions behind the | ||
change that are not reflected in the code itself? | ||
|
||
The “why part” is the most important of the two as it usually cannot be | ||
inferred from the code itself. A well-written PR description will help future | ||
developers (including your future self) to know how to interact and update your | ||
code. | ||
|
||
## How is this tested? | ||
|
||
Describe any tests you have done; especially if test tests are not part of | ||
the unit tests (e.g. local tests). | ||
|
||
**ALWAYS ANSWER THIS QUESTION:** Answer with "N/A" if tests are not applicable | ||
to your PR (e.g. if the PR only modifies comments). Do not be afraid of | ||
answering "Not tested" if the PR has not been tested. Being clear about what | ||
has been done and not done provides important context to the reviewers. |
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.