Skip to content

Add description copy below Connections header on HR page#91641

Merged
amyevans merged 2 commits into
mainfrom
claude-hrConnectionsCopy
May 26, 2026
Merged

Add description copy below Connections header on HR page#91641
amyevans merged 2 commits into
mainfrom
claude-hrConnectionsCopy

Conversation

@MelvinBot

@MelvinBot MelvinBot commented May 25, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

Adds the approved descriptive copy below the "Connections" header on the Workspace HR page, matching the existing pattern on the Accounting page.

The HR page's Section component now uses title and subtitle props (with subtitleMuted styling) instead of a custom renderTitle, consistent with how PolicyAccountingPage renders its Connections section.

The approved copy (from NickTooker): "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work."

Fixed Issues

$ #91032

Tests/QA Steps

  1. Turn on HR integrations from Workspace editor
  2. Navigate to the HR page.
  3. Verify that you see the copy underneath the connections header.
  • 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 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 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.

Display the approved descriptive copy beneath the Connections section
header on the Workspace HR page, matching the pattern used on the
Accounting page for consistency.

Co-authored-by: Yuwen Memon <yuwenmemon@users.noreply.github.com>
@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 1d40a596528..ad76dbd7a91 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7197,7 +7197,7 @@ Fügen Sie weitere Ausgabelimits hinzu, um den Cashflow Ihres Unternehmens zu sc
             title: 'Personalwesen',
             connections: 'Verbindungen',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Verbinden Sie sich mit Ihrem HR-System, um Mitarbeiterdaten zu synchronisieren, Erstattungen automatisch den richtigen Personen zuzuordnen und die Ausgaben Ihres Teams ohne manuellen Aufwand korrekt zu halten.',
             subtitle: 'HR-Tools verbinden und Mitarbeitergenehmigungen synchron halten.',
             connect: 'Verbinden',
             syncNow: 'Jetzt synchronisieren',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index f522fa15619..55acfb145f2 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -6302,7 +6302,7 @@ ${amount} para ${merchant} - ${date}`,
             title: 'HR',
             connections: 'Conexiones',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Conéctate a tu sistema de RR. HH. para sincronizar los datos de empleados, emparejar automáticamente los reembolsos con las personas correctas y mantener los gastos de tu equipo precisos sin trabajo manual.',
             subtitle: 'Conecta herramientas de HR y mantén sincronizadas las aprobaciones de empleados.',
             connect: 'Conectar',
             syncNow: 'Sincronizar ahora',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 208a917ac7e..7231b0e100a 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7222,7 +7222,7 @@ Ajoutez davantage de règles de dépenses pour protéger la trésorerie de l’e
             title: 'RH',
             connections: 'Connexions',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Connectez votre système RH pour synchroniser les données des employé·es, faire correspondre automatiquement les remboursements aux bonnes personnes et garder les dépenses de votre équipe exactes, sans travail manuel.',
             subtitle: 'Connectez vos outils RH et gardez les approbations des employés synchronisées.',
             connect: 'Connecter',
             syncNow: 'Synchroniser maintenant',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 8a6c1ee129c..62d32f966a0 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7184,7 +7184,7 @@ Aggiungi altre regole di spesa per proteggere il flusso di cassa aziendale.`,
             title: 'Risorse umane',
             connections: 'Connessioni',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Collega il tuo sistema HR per sincronizzare i dati dei dipendenti, abbinare automaticamente i rimborsi alle persone giuste e mantenere le spese del tuo team accurate senza lavoro manuale.',
             subtitle: 'Collega gli strumenti HR e mantieni sincronizzate le approvazioni dei dipendenti.',
             connect: 'Connetti',
             syncNow: 'Sincronizza ora',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 07969701db7..ba398ebcb74 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7102,8 +7102,7 @@ ${reportName}
         hr: {
             title: '人事',
             connections: '接続',
-            connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+            connectionsSubtitle: '人事システムと連携して従業員データを同期し、精算を自動で正しい担当者に紐づけることで、手作業なしでチームの経費を正確に管理できます。',
             subtitle: '人事ツールを連携して、従業員の承認を常に同期させます。',
             connect: '接続',
             syncNow: '今すぐ同期',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 985e367958a..110023654bb 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7159,7 +7159,7 @@ er bestedingsregels toe om de kasstroom van het bedrijf te beschermen.`,
             title: 'HR',
             connections: 'Verbindingen',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Verbind met je HR-systeem om werknemersgegevens te synchroniseren, terugbetalingen automatisch aan de juiste personen te koppelen en de uitgaven van je team nauwkeurig te houden zonder handmatig werk.',
             subtitle: 'Koppel HR-tools en houd goedkeuringen van medewerkers gesynchroniseerd.',
             connect: 'Verbinden',
             syncNow: 'Nu synchroniseren',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 5b5a4ff9561..9cbf7309a61 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7154,7 +7154,7 @@ Dodaj więcej zasad wydatków, żeby chronić płynność finansową firmy.`,
             title: 'HR',
             connections: 'Połączenia',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Połącz się ze swoim systemem HR, aby synchronizować dane pracowników, automatycznie dopasowywać zwroty do właściwych osób i utrzymywać wydatki zespołu w porządku bez ręcznej pracy.',
             subtitle: 'Połącz narzędzia HR i utrzymuj zgody pracowników w synchronizacji.',
             connect: 'Połącz',
             syncNow: 'Synchronizuj teraz',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 338a301a0db..cab6b19eef5 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7159,7 +7159,7 @@ Adicione mais regras de gasto para proteger o fluxo de caixa da empresa.`,
             title: 'RH',
             connections: 'Conexões',
             connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+                'Conecte-se ao seu sistema de RH para sincronizar os dados de funcionários, associar automaticamente os reembolsos às pessoas corretas e manter as despesas da sua equipe precisas, sem trabalho manual.',
             subtitle: 'Conecte ferramentas de RH e mantenha as aprovações de funcionários em sincronia.',
             connect: 'Conectar',
             syncNow: 'Sincronizar agora',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 19e48f5cdc7..897ddfc1679 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -6973,8 +6973,7 @@ ${reportName}
         hr: {
             title: '人力资源',
             connections: '连接',
-            connectionsSubtitle:
-                "Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",
+            connectionsSubtitle: '连接您的 HR 系统以同步员工数据,自动将报销匹配到正确的员工,并在无需手动操作的情况下保持团队报销的准确性。',
             subtitle: '连接人力资源工具,保持员工审批同步。',
             connect: '连接',
             syncNow: '立即同步',

Note

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

View workflow run

@codecov

codecov Bot commented May 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/pages/workspace/hr/WorkspaceHRPage.tsx 0.00% <0.00%> (ø)
... and 16 files with indirect coverage changes

@yuwenmemon yuwenmemon requested a review from ShridharGoel May 25, 2026 18:13
@yuwenmemon yuwenmemon marked this pull request as ready for review May 25, 2026 18:15
@yuwenmemon yuwenmemon requested a review from a team as a code owner May 25, 2026 18:15
@melvin-bot melvin-bot Bot requested review from heyjennahay and shawnborton and removed request for a team May 25, 2026 18:15
@melvin-bot

melvin-bot Bot commented May 25, 2026

Copy link
Copy Markdown

@shawnborton 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]

@melvin-bot melvin-bot Bot removed the request for review from a team May 25, 2026 18:15

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

Copy link
Copy Markdown

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: b5b897c9a5

ℹ️ 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".

Comment thread src/languages/es.ts Outdated
Comment on lines +6304 to +6305
connectionsSubtitle:
"Connect to your HR system to sync employee data, auto-match reimbursements to the right people, and keep your team's expenses accurate without the manual work.",

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 Provide localized HR subtitle strings in non-English files

workspace.hr.connectionsSubtitle is set to the English sentence in non-English locale files (for example Spanish here, and similarly in de, fr, it, ja, nl, pl, pt-BR, and zh-hans). For users whose app language is not English, the new copy under the Connections header will display in English, creating a mixed-language UI on the HR page and regressing localization accuracy for a prominently visible string.

Useful? React with 👍 / 👎.

@shawnborton

Copy link
Copy Markdown
Contributor

Can Melvin get us screenshots with playwright?

@yuwenmemon

Copy link
Copy Markdown
Contributor

@MelvinBot Are you able to get us screenshots of this change?

@yuwenmemon

Copy link
Copy Markdown
Contributor

@ShridharGoel, if you don't mind posting screenshots for @shawnborton to review when you test it, it would be appreciated if Melvin is unable to!

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Here are screenshots of the HR page with the new descriptive copy below the "Connections" header:

Desktop (1280×800):
Workspace HR page on desktop viewport showing Connections header with new subtitle text

Mobile (390×844):
Workspace HR page on mobile viewport showing Connections header with new subtitle text

The subtitle text renders correctly on both viewports, with proper muted styling and text wrapping.

@shawnborton

Copy link
Copy Markdown
Contributor

Looks good 👍

@ShridharGoel

ShridharGoel commented May 25, 2026

Copy link
Copy Markdown
Contributor

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 there are no new alerts related to the canBeMissing param for useOnyx
  • 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: mWeb Chrome
iOS: HybridApp Screenshot 2026-05-26 at 11 56 32 PM
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-05-26 at 11 54 54 PM

@ShridharGoel

Copy link
Copy Markdown
Contributor

@MelvinBot Apply the patch present here: #91641 (comment)

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I see the translation patch from Polyglot Parrot and can apply it, but I can only make code changes when directed by the PR author, an assignee, or an existing co-author. To have me implement this, the PR assignee (yuwenmemon) should reply with a request tagging me.

@yuwenmemon

Copy link
Copy Markdown
Contributor

@MelvinBot Apply the patch present here: #91641 (comment)

Co-authored-by: Yuwen Memon <yuwenmemon@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team as a code owner May 25, 2026 20:36
@melvin-bot melvin-bot Bot removed the request for review from a team May 25, 2026 20:36
@melvin-bot

melvin-bot Bot commented May 25, 2026

Copy link
Copy Markdown

@shawnborton 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]

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Applied the Polyglot Parrot translation patch — all 9 non-English language files now have proper translations for connectionsSubtitle (de, es, fr, it, ja, nl, pl, pt-BR, zh-hans).

@melvin-bot

melvin-bot Bot commented May 26, 2026

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #91032 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@amyevans amyevans merged commit 5c3b621 into main May 26, 2026
45 checks passed
@amyevans amyevans deleted the claude-hrConnectionsCopy branch May 26, 2026 18:51
@github-actions

Copy link
Copy Markdown
Contributor

🚧 @amyevans 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/amyevans in version: 9.3.83-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I reviewed the changes in this PR and checked all help site articles under docs/articles/new-expensify/ for any content that would need updating.

No help site changes are required.

This PR adds descriptive subtitle copy below the "Connections" header on the Workspace HR page — a UI-only cosmetic change. No functionality, workflows, or navigation paths changed. The existing help articles (including connections/Rippling.md) describe how-to workflows for connecting HR integrations, not the descriptive text displayed in the UI, so they remain accurate as-is.

@yuwenmemon, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.83-3 🚀

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

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.

6 participants