Skip to content

[No QA][HR Import] Final approver page#91297

Merged
grgia merged 5 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-final-approver-page
May 21, 2026
Merged

[No QA][HR Import] Final approver page#91297
grgia merged 5 commits into
Expensify:mainfrom
software-mansion-labs:feat/merge-hr-final-approver-page

Conversation

@jmusial
Copy link
Copy Markdown
Contributor

@jmusial jmusial commented May 21, 2026

Explanation of Change

This PR adds MergeHRFinalApproverPage to the Merge dev flows. It also unifies Gustos and Merge
Approval Mode pages.

Fixed Issues

$ #90603
PROPOSAL:

Tests

Pre requisites:

  1. Have a workspace with mergeHRConnections flag on
  2. Have a provider coonected (ex. Bamboo)

Steps:

  1. Go to Workspaces -> HR
  2. Click Final approver
  3. Side panel openes, change the approver
  4. New approver is set.

Offline tests

Same as tests

QA Steps

N/A

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 any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • 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)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • 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

Android: Native
Screen.Recording.2026-05-21.at.13.16.53.mov
MacOS: Chrome / Safari
Screen.Recording.2026-05-21.at.13.13.37.mov

@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

@grgia @cristipaval can I have polyglot parrot triggered here please ?

@codecov
Copy link
Copy Markdown

codecov Bot commented May 21, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/pages/workspace/hr/HRProviderCard.tsx 0.00% <0.00%> (ø)
src/libs/actions/connections/MergeHR.ts 16.66% <0.00%> (-3.34%) ⬇️
...ages/workspace/hr/gusto/GustoFinalApproverPage.tsx 0.00% <0.00%> (ø)
...es/workspace/hr/merge/MergeHRFinalApproverPage.tsx 0.00% <0.00%> (ø)
src/pages/workspace/hr/HRFinalApproverPageBase.tsx 0.00% <0.00%> (ø)
... and 42 files with indirect coverage changes

@OSBotify
Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index df51590b..d06de533 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7154,7 +7154,7 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             connectionDescription: (providerName: string) => `Verbinden Sie ${providerName}, um Mitarbeitergenehmigungen mit Ihrem Workspace zu synchronisieren.`,
             approvalMode: 'Genehmigungsmodus',
             finalApprover: 'Endgültige:r Genehmiger:in',
-            providerFinalApprover: (providerName: string) => `${providerName} endgültige:r Genehmiger:in`,
+            providerFinalApprover: (providerName: string) => `${providerName} Endgenehmigende*r`,
             notSet: 'Nicht festgelegt',
             approvalModeDescription: (providerName: string) => `Mitglieder und Manager sind für die Synchronisation mit ${providerName} eingerichtet.`,
             approvalModeWarningTitle: 'Genehmigungsmodus ändern?',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index 82a6b681..b25378ba 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6269,7 +6269,7 @@ ${amount} para ${merchant} - ${date}`,
             connectionDescription: (providerName: string) => `Conecta ${providerName} para mantener sincronizadas las aprobaciones de empleados con tu espacio de trabajo.`,
             approvalMode: 'Modo de aprobación',
             finalApprover: 'Aprobador final',
-            providerFinalApprover: (providerName: string) => `Aprobador final de ${providerName}`,
+            providerFinalApprover: (providerName: string) => `aprobador final de ${providerName}`,
             notSet: 'No configurado',
             approvalModeDescription: (providerName: string) => `Los miembros y gerentes están configurados para sincronizarse con ${providerName}.`,
             approvalModeWarningTitle: '¿Cambiar modo de aprobación?',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7a6c21a7..967df754 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7141,7 +7141,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             connectionDescription: (providerName: string) => `Collega ${providerName} per mantenere sincronizzate le approvazioni dei dipendenti con il tuo spazio di lavoro.`,
             approvalMode: 'Modalità di approvazione',
             finalApprover: 'Approvatore finale',
-            providerFinalApprover: (providerName: string) => `Approvatore finale di ${providerName}`,
+            providerFinalApprover: (providerName: string) => `approvatore finale ${providerName}`,
             notSet: 'Non impostato',
             approvalModeDescription: (providerName: string) => `I membri e i responsabili sono configurati per la sincronizzazione con ${providerName}.`,
             approvalModeWarningTitle: 'Cambiare modalità di approvazione?',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 50251644..9ed7a093 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7060,7 +7060,7 @@ ${reportName}
             connectionDescription: (providerName: string) => `${providerName}を接続して、従業員の承認をワークスペースと同期させましょう。`,
             approvalMode: '承認モード',
             finalApprover: '最終承認者',
-            providerFinalApprover: (providerName: string) => `${providerName}の最終承認者`,
+            providerFinalApprover: (providerName: string) => `${providerName} 最終承認者`,
             notSet: '未設定',
             approvalModeDescription: (providerName: string) => `メンバーとマネージャーは ${providerName} と同期するように設定されています。`,
             approvalModeWarningTitle: '承認モードを変更しますか?',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 6cb77fa2..58090079 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7116,7 +7116,7 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
             connectionDescription: (providerName: string) => `Verbind ${providerName} om goedkeuringen van werknemers gesynchroniseerd te houden met je werkruimte.`,
             approvalMode: 'Goedkeuringsmodus',
             finalApprover: 'Eindgoedkeurder',
-            providerFinalApprover: (providerName: string) => `${providerName} eindgoedkeurder`,
+            providerFinalApprover: (providerName: string) => `Laatste ${providerName}-fiatteur`,
             notSet: 'Niet ingesteld',
             approvalModeDescription: (providerName: string) => `Leden en managers zijn ingesteld om te synchroniseren met ${providerName}.`,
             approvalModeWarningTitle: 'Goedkeuringsmodus wijzigen?',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 94347b63..6ac6c605 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7111,7 +7111,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             connectionDescription: (providerName: string) => `Połącz ${providerName}, aby synchronizować akceptacje pracowników z Twoim miejscem pracy.`,
             approvalMode: 'Tryb zatwierdzania',
             finalApprover: 'Ostateczny zatwierdzający',
-            providerFinalApprover: (providerName: string) => `Ostateczny zatwierdzający ${providerName}`,
+            providerFinalApprover: (providerName: string) => `Ostateczny akceptujący ${providerName}`,
             notSet: 'Nie ustawiono',
             approvalModeDescription: (providerName: string) => `Członkowie i menedżerowie są skonfigurowani do synchronizacji z ${providerName}.`,
             approvalModeWarningTitle: 'Zmienić tryb zatwierdzania?',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 5634690d..bbb0b7a8 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7116,7 +7116,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             connectionDescription: (providerName: string) => `Conecte ${providerName} para manter as aprovações de funcionários sincronizadas com seu workspace.`,
             approvalMode: 'Modo de aprovação',
             finalApprover: 'Aprovador final',
-            providerFinalApprover: (providerName: string) => `Aprovador final de ${providerName}`,
+            providerFinalApprover: (providerName: string) => `aprovador final de ${providerName}`,
             notSet: 'Não definido',
             approvalModeDescription: (providerName: string) => `Membros e gerentes estão configurados para sincronizar com ${providerName}.`,
             approvalModeWarningTitle: 'Alterar modo de aprovação?',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 0d1f75eb..725b24a7 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6933,7 +6933,7 @@ ${reportName}
             connectionDescription: (providerName: string) => `连接 ${providerName},以在您的工作区中同步员工审批。`,
             approvalMode: '审批模式',
             finalApprover: '最终审批人',
-            providerFinalApprover: (providerName: string) => `${providerName}最终审批人`,
+            providerFinalApprover: (providerName: string) => `${providerName} 最终审批人`,
             notSet: '未设置',
             approvalModeDescription: (providerName: string) => `成员和管理员已设置为与 ${providerName} 同步。`,
             approvalModeWarningTitle: '更改审批模式?',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@jmusial jmusial marked this pull request as ready for review May 21, 2026 11:49
@jmusial jmusial requested review from a team as code owners May 21, 2026 11:49
@melvin-bot melvin-bot Bot requested review from bernhardoj and heyjennahay and removed request for a team May 21, 2026 11:49
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented May 21, 2026

@bernhardoj Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cba2d405f2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

beta: CONST.BETAS.MERGE_HR,
isConnected: isMergeHRConnected,
getCurrentFinalApprover: (policy) => policy?.connections?.merge_hris?.config?.finalApprover ?? null,
getProviderName: (policy) => getConnectedHRProvider(policy)?.displayName ?? CONST.POLICY.CONNECTIONS.NAME_USER_FRIENDLY.merge_hris,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Resolve provider name from Merge connection config

Using getConnectedHRProvider(policy) here can return Gusto or Zenefits because that helper picks the first connected HR integration, so when a workspace has multiple HR connections the Merge final-approver page can render the wrong header label (for example, showing a Gusto title on the Merge route). This page should derive its provider name from the Merge connection itself (e.g., policy.connections.merge_hris.config.integration) so the title always matches the active Merge provider.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a user should only have one HR integration connected

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wondering about the case when a policy deletes one connection and adds a second, do we have both objects

@grgia grgia requested review from cristipaval and grgia May 21, 2026 12:01
@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

@grgia
Copy link
Copy Markdown
Contributor

grgia commented May 21, 2026

Screenshot 2026-05-21 at 1 36 58 PM Screenshot 2026-05-21 at 1 37 07 PM

@jmusial any idea why Approval mode is blank

edit im tired it's #91202

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

edit im tired it's #91202

Yup, they're separate PRs

@bernhardoj
Copy link
Copy Markdown
Contributor

I think we want to show the error for the final approver too, similar to the approval mode

{card.isConnected && !!finalApproverRoute && (
<OfflineWithFeedback pendingAction={card.config?.pendingFields?.finalApprover}>

@grgia
Copy link
Copy Markdown
Contributor

grgia commented May 21, 2026

@jmusial the locked workspace flows still let's me click through settings

Screen.Recording.2026-05-21.at.3.24.19.PM.mov

<OfflineWithFeedback pendingAction={card.config?.pendingFields?.finalApprover}>
<OfflineWithFeedback
pendingAction={card.config?.pendingFields?.finalApprover}
errors={card.config?.errorFields?.approvalMode}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should the error be .finalApprover too

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@jmusial
Copy link
Copy Markdown
Contributor Author

jmusial commented May 21, 2026

approvalMode

Which approval mode do you have set? If it's Custom I believe you should be able to change

@grgia
Copy link
Copy Markdown
Contributor

grgia commented May 21, 2026

It was set to nothing"". We can leave that as is for now if that was the existing behavior for gusto

@bernhardoj
Copy link
Copy Markdown
Contributor

bernhardoj commented May 21, 2026

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • 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 shown in the product is localized by adding it to src/languages/* files and using the translation method
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • 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)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • 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 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.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
android.mp4
Android: mWeb Chrome
android.mweb.mp4
iOS: HybridApp
ios.mp4
iOS: mWeb Safari
ios.mweb.mp4
MacOS: Chrome / Safari
web.mp4

@melvin-bot melvin-bot Bot requested a review from grgia May 21, 2026 15:22
@grgia grgia merged commit c76b3dd into Expensify:main May 21, 2026
42 of 43 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

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

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/grgia in version: 9.3.79-1 🚀

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

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants