Automation/10321-chanel-release-issue-assign-flagship-mobile-approver-members

[IsraelleHub]

Description of Change

The current release issue is not tagging member of flagship-mobile-release-approvers group. Instead it tags members og the flagship-mobile-release-admin group eventough the release_branch_issue workflow is tagging flagship-mobile-release-approvers group

Test:

Test was done by cloning the release_ticket.md file and by using a test workflow.
For the clone release_ticket.md file, The GitHub username hardcoded as assignee was : IsraelleHub because we didn't want to alert other approvers.

Test Results:

The current flagship-mobile-release-approvers group only has 3 members (narin, IsraelleHub, timwright12).
After running the test workflow, it assigned our release issue ticket with those assignee only as you see in this ticket

Screenshots/Video

Testing

• Tested on iOS
• Tested on Android

Reviewer Validations

PR Checklist

Reviewer: Confirm the items below as you review

• PR is connected to issue(s)
• Tests are included to cover this change (when possible)
• No magic strings (All string unions follow the Union -> Constant type pattern)
• No secrets or API keys are checked in
• All imports are absolute (no relative imports)
• New functions and Redux work have proper TSDoc annotations

For QA

Run a build for this branch

[timwright12]

@IsraelleHub can you add a confirmation that the assignment in CI is working before we update this template?