[No QA] Auto-file staging retest request for cherry-picked blocker fixes

[jasperhuangg]

Explanation of Change

When a deploy-blocker fix is cherry-picked to staging, the deployer currently files a Slack #retests request by hand. This does it automatically: a new deploy job fires on a staging cherry-pick (once all platforms land) when the cherry-picked PR is on the current StagingDeployCash checklist and links a deploy-blocker issue on it, then POSTs the retest request to the Slack webhook.

The webhook URL is loaded from 1Password (Repository-Secrets/SLACK_RETEST_WEBHOOK in the Mobile-Deploy-CI vault), not the code.

How it works

1. A staging deploy finishes on all platforms and was triggered by a cherry-pick.
2. The job resolves the cherry-picked PR from the deploy's commit range.
3. It checks that PR is on the current StagingDeployCash checklist and links a deploy-blocker issue on it.
4. If so, it POSTs the retest request to the Slack #retests workflow.
5. It drops a marker comment on the PR so a re-deploy won't file a duplicate.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/574358
PROPOSAL:

Tests

This is a deploy-workflow change with no app-facing UI. It only runs inside the staging deploy for a cherry-pick, so it can't be exercised in the local dev environment. Logic is covered by unit tests:

1. Run npx jest tests/unit/createRetestRequestForCPTest.ts.
2. Verify all tests pass (commit-trailer parsing, linked-issue parsing, Slack payload mapping, dedupe marker).

• Verify that no errors appear in the JS console

Offline tests

N/A, this runs in CI during a deploy, there is no offline client behavior.

QA Steps

N/A. This only runs in the staging deploy workflow when a deploy-blocker fix is cherry-picked to staging, so it can't be triggered on demand by QA. Title includes [No QA].

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

N/A, this is a CI/deploy workflow change with no app UI.

Android: Native

N/A

Android: mWeb Chrome

N/A

iOS: Native

N/A

iOS: mWeb Safari

N/A

MacOS: Chrome / Safari

N/A

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f9a96ce8c8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[jasperhuangg]

gonna hold off on merging/CPing this to staging until the next time I need to run a CP myself so I can test this out.

[jasperhuangg]

Actually, this should hit staging after this next deploy, so I think we should be good to just merge.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 jasperhuangg has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #96103.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-e5e6b85b45c-469fb75-c6fec9776e631423faf3085dc712bbbab8641158/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-e5e6b85-469fb75-f94f69bb90ccb32216e37abf584e2765122cdf2d/index.html

Web 🕸️
https://96103.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/jasperhuangg in version: 9.4.35-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[MelvinBot]

🤖 No help site changes required.

I reviewed the changes in this PR and they do not require any updates to Expensify's help site files under App/docs/articles.

Why: This is an internal CI/deploy-workflow change. It adds a script (scripts/createRetestRequestForCP.ts) and a deploy.yml job that automatically files a Slack #retests request when a deploy-blocker fix is cherry-picked to staging. As the PR description itself notes, there is no app-facing UI — it only runs inside the staging deploy workflow. The help site documents customer-facing product behavior (features, billing, workspaces, integrations, etc.), and this change touches none of that. A search of App/docs/articles for related terms (retest, cherry-pick, deploy blocker) returned no matches.

Since no changes are needed, I did not create a draft help site PR — there is nothing to link.

@jasperhuangg, please confirm you agree no help site updates are needed here. If you believe a customer-facing doc is affected, let me know which behavior and I'll draft the update.