manager icon indicating copy to clipboard operation
manager copied to clipboard

upcoming: [M3-7770]: Placement Groups types update, part 2

Open abailly-akamai opened this issue 1 year ago โ€ข 0 comments

Description ๐Ÿ“

Highlight the Pull Request's context and intentions.

Changes ๐Ÿ”„

List any change relevant to the reviewer.

  • ...
  • ...

Target release date ๐Ÿ—“๏ธ

Please specify a release date to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview ๐Ÿ“ท

Include a screenshot or screen recording of the change

:bulb: Use <video src="" /> tag when including recordings in table.

Before After
๐Ÿ“ท ๐Ÿ“ท

How to test ๐Ÿงช

Prerequisites

(How to setup test environment)

  • ...
  • ...

Reproduction steps

(How to reproduce the issue, if applicable)

  • ...
  • ...

Verification steps

(How to verify changes)

  • ...
  • ...

As an Author I have considered ๐Ÿค”

Check all that apply

  • [ ] ๐Ÿ‘€ Doing a self review
  • [ ] โ” Our contribution guidelines
  • [ ] ๐Ÿค Splitting feature into small PRs
  • [ ] โž• Adding a changeset
  • [ ] ๐Ÿงช Providing/Improving test coverage
  • [ ] ๐Ÿ” Removing all sensitive information from the code and PR description
  • [ ] ๐Ÿšฉ Using a feature flag to protect the release
  • [ ] ๐Ÿ‘ฃ Providing comprehensive reproduction steps
  • [ ] ๐Ÿ“‘ Providing or updating our documentation
  • [ ] ๐Ÿ•› Scheduling a pair reviewing session
  • [ ] ๐Ÿ“ฑ Providing mobile support
  • [ ] โ™ฟ Providing accessibility support

Commit message and pull request title format standards

Note: Remove this section before opening the pull request Make sure your PR title and commit message on squash and merge are as shown below

<commit type>: [JIRA-ticket-number] - <description>

Commit Types:

  • feat: New feature for the user (not a part of the code, or ci, ...).
  • fix: Bugfix for the user (not a fix to build something, ...).
  • change: Modifying an existing visual UI instance. Such as a component or a feature.
  • refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.
  • test: New tests or changes to existing tests. Does not change the production code.
  • upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.

Example: feat: [M3-1234] - Allow user to view their login history


abailly-akamai avatar Feb 16 '24 01:02 abailly-akamai