Feature/action 1

[goutamdh]

Overview

REPLACE THIS with what's in the PR. Is there anything the reviewer should know?

Reviewee Checklist

Complete this checklist if you are submitting the PR.

• The PR is named correctly.
  • The ticket number should be in PR title. For Release -> Master something else...
• The PR is merging to correct branch.
• The PR has been checked out and confirmed to run locally.
• Components impacted by shared file changes have been tested to ensure there are no breaking changes.
• The code is readable.
  • Checked for too many nested conditions.
  • Functions and variables named appropriately. (eg. Avoid use of acronyms)
• There are no commented-out blocks of code.
  • Temporarily commented-out code is an exception. It should be noted.

Reviewer Checklist

Complete this checklist if you are the reviewer.

• The PR is named correctly.
  • The ticket number should be in PR title. For Release -> Master something else...
• The PR is merging to correct branch?
• There are no changes in this PR that are outside the scope of the ticket.
• The PR has been checked out and confirmed to run locally.
• Components impacted by shared file changes have been tested to ensure there are no breaking changes.
• The code is readable.
  • Checked for too many nested conditions.
  • Functions and variables named appropriately. (eg. Avoid use of acronyms)
• There are no commented-out blocks of code.
  • Temporarily commented-out code is an exception. It should be noted.

Merge Instructions

When merging PRs to Integration and Master/Main/Trunk, use the Squash merge option.

Tips

• Press "." to open this PR in a browser-based vscode.

FOR CONFLUENCE

Labels

Use labels to signal the state of Pull Requests.