Skip to content

[No QA] Merge Main - #103093

Merged
stephanieelliott merged 2260 commits into
helpsite-perdiem-control-onlyfrom
main
Oct 5, 2026
Merged

stephanieelliott merged 2260 commits into
helpsite-perdiem-control-onlyfrom
main

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[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.
  • If the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

TMisiukiewicz and others added 30 commits October 2, 2026 08:52
…mModals

[Batch 6] Migrate GPS trip ConfirmModal usages to useConfirmModal
…4-app-policy-draft-leaf

Fix import/no-cycle - part 14
…eport-pr1

Part 1 - Remove onyx connect for the key: ONYXKEYS.COLLECTION.REPORT in Parser lib
…is unlocking a locked account

Co-authored-by: DylanDylann <DylanDylann@users.noreply.github.com>
Co-authored-by: DylanDylann <DylanDylann@users.noreply.github.com>
After AddWorkEmail switches the login to the work email, going back to the
work email screen and resubmitting compared the prefilled email with itself
and showed the same-as-signup error. Restore shouldValidate: false instead of
resending, and only show the signup-email message for public-domain emails.

Co-authored-by: TaduJR <TaduJR@users.noreply.github.com>
…ined

An Insights search skips pending writes, so one sent alongside a replayed
RequestMoney can be answered before the server saw the expense. Counting
pendingAction in the fingerprint moves the counter again once the server
clears it, so the chart refetches after the write lands.

Joining a workspace brings its members' spend into the chart without
changing any local expense, so the refresh key now includes the policy IDs.
…b-focus

# Conflicts:
#	src/ONYXKEYS.ts
#	src/libs/actions/OnyxDerived/ONYX_DERIVED_VALUES.ts
#	src/types/onyx/DerivedValues.ts
#	src/types/onyx/index.ts
…eryByHashOnyxConnect

# Conflicts:
#	src/libs/actions/IOU/index.ts
Co-authored-by: TaduJR <TaduJR@users.noreply.github.com>
Co-authored-by: Aimane Chnaif <aimane-chnaif@users.noreply.github.com>
Classic exports amounts like "299,393.00". Number() returned NaN for these, so the import silently dropped Flag amounts over and Require receipts over. Move the parsing into ImportCategoriesUtils and add tests that import a Classic export row.

Co-authored-by: daledah <daledah@users.noreply.github.com>
An edit marks only the edited field in pendingFields and leaves
pendingAction unset, so the previous fix never moved the counter for it.
Tested on web: an amount edited offline left the chart at the old total.
The fingerprint now tracks whether the expense has any pending write,
from either field.
@stephanieelliott
stephanieelliott requested review from a team as code owners October 5, 2026 22:47
@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team October 5, 2026 22:47
@melvin-bot

melvin-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-05T22:57:23.906580Z 52e1a25 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

This PR adds a new Onyx.connectWithoutView call, so I've requested a review from the Onyx performance reviewers (@tgolen, @mountiny, @luacmartins, @chuckdries) — a review from any one of them is enough. Please add a link in your PR description to the Slack discussion where the @frontend-performance team approved using connectWithoutView here.

@melvin-bot

melvin-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @lschurr

@melvin-bot
melvin-bot Bot requested review from lschurr and madmax330 and removed request for a team October 5, 2026 22:48
@melvin-bot

melvin-bot Bot commented Oct 5, 2026

Copy link
Copy Markdown

@madmax330 @lschurr One of you needs to 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]

@OSBotify

OSBotify commented Oct 5, 2026

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:

The diff is too large to include in this comment (262KB), so I've created a gist for you:

📋 View the translation diff here 📋

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply, or directly by running gh gist view --raw 1101a2d5c17a23f1282ced44edc317ff | git apply 😉

View workflow run

@codecov

codecov Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

Codecov Report

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

Files with missing lines Coverage Δ
src/App.tsx 100.00% <ø> (ø)
src/CONST/index.ts 95.83% <ø> (ø)
src/DeepLinkHandler.tsx 92.53% <100.00%> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/ROUTES.ts 31.19% <100.00%> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/ApproverSelectionList.tsx 95.83% <ø> (ø)
src/components/ArchivedReportFooter.tsx 71.42% <100.00%> (ø)
...ttachmentCarousel/AttachmentCarouselView/index.tsx 0.00% <ø> (ø)
...nents/Avatar/connected/PolicyExpenseChatAvatar.tsx 100.00% <100.00%> (ø)
... and 231 more

@stephanieelliott
stephanieelliott merged commit e6f2e1f into helpsite-perdiem-control-only Oct 5, 2026
141 checks passed
@github-actions github-actions Bot changed the title Merge Main [No QA] Merge Main Oct 5, 2026
@OSBotify

OSBotify commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

A preview of your ExpensifyHelp changes have been deployed to https://dd0536eb.helpdot.pages.dev ⚡️

Updated articles:

description: Configure your workspace approval and submission workflows to match your team's needs.
keywords: [New Expensify, workflows, workflows tabs, submissions, approvals, payments, advanced, approval workflows, delay submission, add approver, connect bank, workspace settings, submission frequency, authorized payer, mark as paid, payer, prevent self-approvals, auto-approve compliant reports, auto-pay approved reports, multiple approval paths, shared approver, forward to different approver]
internalScope: Audience is Workspace Admins. Covers configuring approval, submission, reimbursement, and advanced report workflows including choosing an authorized payer; does not cover connecting a bank account.
description: Configure your workspace submission, approval, and payment workflows to match your team's needs.

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.

Duplicate YAML frontmatter keys: description, keywords, and internalScope are each defined twice (lines 3-5 and 6-8). YAML frontmatter must contain each metadata key only once (HELP_AUTHORING_GUIDELINES.md Section 3). Remove this duplicate block (lines 6-8) and keep a single description, keywords, and internalScope.

description: Require report approvals in your Expensify workspace, including setting approval thresholds and over-limit approvers.
keywords: [New Expensify, approvals, report approvals, approving reports, approval workflow, workspace workflows, approver, final approver, approval chain, approval threshold, approval limit, over-limit approval, report amount limit, dollar limit approver, reassign approver, automatic approver reassignment, change approver workflow, automatic approval, approval audit, category approver, tag approver, category rules, tag rules, invite member to approval workflow, invite new user approval workflow, import workflows, import approval workflows, bulk approval workflows, spreadsheet import, multiple approval paths, multiple approvers, shared approver, audit team approver, forward to different approver, approval path per submitter, edit approvals in Expensify Classic]
internalScope: Audience is Workspace Admins and People Admins, covers enabling approvals and building default, custom, and multi-path approval workflows in New Expensify, does not cover Category and Tag approver setup or connecting a bank account.
keywords: [New Expensify, approvals, report approvals, approving reports, approval workflow, workspace workflows, approver, final approver, approval chain, approval threshold, approval limit, over-limit approval, report amount limit, dollar limit approver, remove limit, remove approval limit, reassign approver, automatic approver reassignment, change approver workflow, approval workflow change message, admins room system message, automatic approval, approval audit, category approver, tag approver, category rules, tag rules, invite member to approval workflow, invite new user approval workflow, import workflows, import approval workflows, bulk approval workflows, spreadsheet import]

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.

Duplicate YAML keywords key: keywords is defined twice (line 4 and line 6). Metadata keys must appear only once in the frontmatter (HELP_AUTHORING_GUIDELINES.md Section 3). Merge into a single keywords list and remove the duplicate.

Only the actions available to you appear. **Book travel** appears only when Expensify Travel is enabled on your active workspace, and it opens the same booking tool as the **Book travel** option in the **➕ Create** button.

Learn how to [enable Expensify Travel on a workspace](/articles/travel/company-setup/Enable-Travel-on-a-Workspace).
## How to jump to a domain page using Search

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.

Structure/readability: This ## How to jump to a domain page using Search heading immediately follows the previous section's Learn how to... line with no blank line or --- separator between the two sections. Add a blank line (and the --- section divider used between the other sections) before this heading so the sections render correctly and stay scannable.

---

## What happens after you create an Agent from a template
## What Description Dan Does

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.

Heading casing + trailing space: Use sentence case to match the other headings in this article (## What TipMaster does, ## What Translator Tess does). Change ## What Description Dan Does to ## What Description Dan does and remove the trailing whitespace.


If your workspace isn't connected to DualEntry yet, learn how to [connect to DualEntry](/articles/new-expensify/connections/dualentry/Connect-to-DualEntry).

## Which DualEntry vendors are available in Expensify

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.

Heading rule: Content ## headings must start with an action verb or an approved question word (How, What, Where, Who, Why, When) per HELP_AUTHORING_GUIDELINES.md Section 2. "Which" is not an approved starter. Rephrase, e.g. ## What DualEntry vendors are available in Expensify.

- Both **Workspace Admins** and **People Admins** can enable and configure Approvals.

Learn how to [configure Approvals](/articles/new-expensify/workspaces/Add-Approvals).
Learn how to [enable Approvals](https://help.expensify.com/articles/new-expensify/workspaces/Add-Approvals) and [configure Approvals](/articles/new-expensify/workspaces/Add-Approvals) on your workspace.

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.

Link formatting: Cross-links must use relative links, not full URLs (HELP_AUTHORING_GUIDELINES.md Section 7). The enable Approvals link uses a full https://help.expensify.com/... URL. Change it to the relative form /articles/new-expensify/workspaces/Add-Approvals. Also note this line now links the same article twice ("enable Approvals" and "configure Approvals") — consider consolidating to a single link to avoid redundant linking.

- A company account into a personal account.
- Two company accounts on private domains.
- A company account into a personal account while logged in from the personal account.
- Two company accounts on private domains if both private domains are [verified on Expensify](https://help.expensify.com/articles/new-expensify/domains/Claim-and-Verify-a-Domain). If only one of the private domains is verified, then you can sign into the Expensify account with the verified private domain, then merge the other Expensify account without the verified private domain.

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.

Link formatting: Use a relative link instead of a full URL (HELP_AUTHORING_GUIDELINES.md Section 7). Change https://help.expensify.com/articles/new-expensify/domains/Claim-and-Verify-a-Domain to /articles/new-expensify/domains/Claim-and-Verify-a-Domain.

---

## How to Confirm the Vendor Email in QuickBooks Online
## How to Fix the Name Conflict in QuickBooks Online

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.

Heading casing: Headings should use sentence case, not Title Case (HELPSITE_NAMING_CONVENTIONS.md / HELP_AUTHORING_GUIDELINES.md heading examples use sentence case). Change ## How to Fix the Name Conflict in QuickBooks Online to ## How to fix the name conflict in QuickBooks Online.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This is a "Merge Main" PR that brings a large batch of HelpDot updates from main into the helpsite-perdiem-control-only branch. 32 article files changed, ranging from one brand-new article (DualEntry vendor matching) to substantial rewrites (Greenhouse, both ONL583 QuickBooks Online error articles, Agent templates) and many smaller, high-quality additions (bank account validation, approvals, distance rates, NetSuite, Search-driven navigation, travel). Overall quality is high: strong task-based headings, excellent internalScope/keyword metadata, consistent navigation phrasing, proper bold UI labels, and correct three-dots (vertical ellipsis) usage. A handful of merge artifacts and link/heading-casing issues should be cleaned up before publishing.

Scores Summary

  • Readability: 9/10 - Clear, scannable, action-oriented steps and well-structured FAQs. The new DualEntry article, Greenhouse rewrite, and bank-account validation updates read very cleanly. Minor inconsistencies (Agent/agent casing in Use-Agent-Templates) are the only distractions.
  • AI Readiness: 7/10 - Task-based headings, full feature names, realistic search phrases, and rich internalScope are excellent. Held back by two files with duplicate/conflicting YAML keys introduced by the merge (Add-Approvals.md has two keywords; Workspace-Workflows.md has two each of description, keywords, and internalScope), which undermine metadata reliability.
  • Style Compliance: 7/10 - UI terminology, button bolding, and navigation phrasing are consistently correct. Deductions for several full https://help.expensify.com/... links where relative links are required, and Title Case headings in both ONL583 articles plus "What Description Dan Does" in Use-Agent-Templates.

Key Findings

  • Merge artifacts (duplicate YAML keys, must fix): Workspace-Workflows.md contains two description, two keywords, and two internalScope lines with conflicting content; Add-Approvals.md contains two keywords lines. Collapse to a single authoritative set each.
  • Relative-link rule violations: Workspace-Workflows.md, Validate-a-Business-Bank-Account.md, Merge-Accounts.md, and all six travel articles use full https://help.expensify.com/... URLs instead of required relative links. Some files mix both styles (e.g. Workspace-Workflows links to Add-Approvals once by full URL and once relative).
  • Heading casing: Both ONL583 articles use Title Case headings (e.g. "How to Fix the Name Conflict in QuickBooks Online", "Can a Customer or Employee Record Cause This Error?"), and Use-Agent-Templates.md adds "What Description Dan Does" (Title Case) alongside sibling Sentence-case headings like "What TipMaster does".
  • Formatting nit: In Navigating-New-Expensify.md, the "Learn how to enable Expensify Travel" line runs directly into the next "How to jump to a domain page using Search" heading with no blank line between them.
  • Positives: The new Manage-Vendor-Matching-for-DualEntry.md is an exemplary article (single workflow, complete metadata, task-based headings, clean relative cross-link, well-scoped FAQ). The ONL583 rewrites are a genuine accuracy improvement (correct root cause and fix). Navigation/Search, travel, and bank-account additions all follow the "on the left on web, on the bottom on mobile" convention and bold UI labels correctly.

Recommendations

  • Priority 1: Resolve the duplicate YAML frontmatter keys in Workspace-Workflows.md and Add-Approvals.md, keeping one accurate description/keywords/internalScope each.
  • Priority 2: Convert full help.expensify.com URLs to relative links across Workspace-Workflows, Validate-a-Business-Bank-Account, Merge-Accounts, and the six travel articles.
  • Priority 3: Normalize headings to Sentence case in both ONL583 articles and fix "What Description Dan Does" to "What Description Dan does"; standardize Agent/agent casing and remove trailing whitespace in Use-Agent-Templates.
  • Minor: Add the missing blank line before "How to jump to a domain page using Search" in Navigating-New-Expensify.

Files Reviewed

  • Manage-Vendor-Matching-for-DualEntry.md (new) - exemplary, no issues.
  • Configure-DualEntry.md - clean relative cross-link added.
  • Navigating-New-Expensify.md - strong content; missing blank line before one heading.
  • Validate-a-Business-Bank-Account.md - excellent detail; one full-URL link to fix.
  • Connect-a-Business-Bank-Account.md / Share-a-Business-Bank-Account.md - accurate status-badge updates, relative links, good screenshot purpose.
  • Add-Approvals.md - great new multi-path section; duplicate keywords key to fix.
  • Workspace-Workflows.md - useful additions; duplicate YAML keys and a full-URL link to fix.
  • Create-and-manage-expense-tags.md / Set-distance-rates.md - clean, compliant additions.
  • AI-Agent-Capabilities.md / AI-Agent-Triggers.md - consistent, compliant additions.
  • Use-Agent-Templates.md - good rewrite; one Title Case heading, Agent/agent casing, trailing whitespace.
  • Connect-Greenhouse-to-Expensify.md - strong rewrite into task-based sections with good screenshot purposes.
  • Connect-ChatGPT-to-Expensify-Using-MCP.md - terminology updated consistently (plugin).
  • Configure-Netsuite.md - clear new split-exports settings and FAQs; Sentence-case toggle labels correct.
  • ONL583-Export-Error.md (new-expensify and expensify-classic) - accuracy much improved; Title Case headings to normalize.
  • Import-Personal/Company-Card-Transactions-From-a-Spreadsheet.md / Manage-Personal-Cards.md - clean, compliant.
  • Attach-and-edit-receipts-on-expenses.md / Distance-Expenses.md / Managing-Expenses-in-a-Report.md - accurate, compliant updates.
  • Delegate-when-out-of-office.md / Merge-Accounts.md - good; Merge-Accounts has one full-URL link to fix.
  • Manage-Domain-Members.md - new vacation-delegate section; task-based heading and FAQ, compliant.
  • travel/booking-travel/* (6 files) - consistent Search-to-book addition; all use full URLs that should be relative.

Note: This is a summary review. Scores and findings are based only on the diff against the PR base.

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.