Closes:
What specific problem were you aiming to address, and how did you successfully resolve it? If tests were not uploaded for this pull request or if coverage decreased, please provide an explanation for the change.
All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.
I have...
- included the correct type prefix in the PR title
- added
!to the type prefix if API or client breaking change - targeted the correct branch (see PR Targeting)
- provided a link to the relevant issue or specification
- followed the guidelines for building modules
- included the necessary unit and integration tests
- included comments for documenting Go code
- updated the relevant documentation or specification
- reviewed "Files changed" and left comments if necessary
- confirmed all CI checks have passed
All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.
I have...
- confirmed the correct type prefix in the PR title
- confirmed
!in the type prefix if API or client breaking change - confirmed all author checklist items have been addressed
- reviewed state machine logic
- reviewed API design and naming
- reviewed documentation is accurate
- reviewed tests and test coverage
- manually tested (if applicable)
Are there any specific considerations to take into account when deploying these changes? This may include new dependencies, scripts that need to be executed, or any aspects that can only be evaluated in a deployed environment.
Please provide any relevant before and after screenshots by uploading them here. Additionally, demo videos can be highly beneficial in demonstrating the process.