Skip to content

[No QA] Stephanieelliott patch 16#74530

Merged
stephanieelliott merged 1692 commits intotest-imagefrom
stephanieelliott-patch-16
Nov 7, 2025
Merged

[No QA] Stephanieelliott patch 16#74530
stephanieelliott merged 1692 commits intotest-imagefrom
stephanieelliott-patch-16

Conversation

@stephanieelliott
Copy link
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
    • MacOS: Desktop
  • 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 verified there are no new alerts related to the canBeMissing param for useOnyx
  • 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
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

mountiny and others added 30 commits November 4, 2025 23:34
…ement-button-remove-back-to-forward-to

SettlementButton - migrate redirect to ROUTES.SETTINGS_CONTACT_METHOD_VERIFY_ACCOUNT (removal of backTo)
Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.POLICY_CATEGORIES in src/libs/actions/IOU.ts
Remove Review button from Inbox and Reports page
…rash-when-pressing-the-wide-rhp-overlay

Revert "Fix second overlay is shown when closing the wide RHP"
Implementing optimistic violations for workspace categories and tags.
gelocraft and others added 3 commits November 7, 2025 01:39
chore(eslint): enable unicorn/prefer-set-has lint rule
Update avatar for concierge-ai
@stephanieelliott stephanieelliott requested review from a team as code owners November 7, 2025 04:17
@stephanieelliott stephanieelliott merged commit e9cd317 into test-image Nov 7, 2025
30 of 31 checks passed
@stephanieelliott stephanieelliott deleted the stephanieelliott-patch-16 branch November 7, 2025 04:17
@melvin-bot melvin-bot bot requested review from mollfpr and removed request for a team November 7, 2025 04:17
@melvin-bot
Copy link

melvin-bot bot commented Nov 7, 2025

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

@OSBotify
Copy link
Contributor

OSBotify commented Nov 7, 2025

🦜 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/it.ts b/src/languages/it.ts
index b70b72b8..4d9311b7 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -4822,7 +4822,6 @@ ${amount} per ${merchant} - ${date}`,
                 defaultCard: 'Carta predefinita',
                 downgradeTitle: `Impossibile effettuare il downgrade dello spazio di lavoro`,
                 downgradeSubTitle: `Questo workspace non può essere declassato perché sono collegati più flussi di carte (escludendo le carte Expensify). Per favore <a href="#">mantieni solo un feed di carte</a> per procedere.`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `Per favore, aggiungi l'account in ${connection} e sincronizza nuovamente la connessione.`,
                 expensifyCardBannerTitle: 'Ottieni la Expensify Card',
                 expensifyCardBannerSubtitle:
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 5bed328f..f4eeb29f 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -4780,7 +4780,6 @@ ${date} - ${merchant}に${amount}`,
                 defaultCard: 'デフォルトカード',
                 downgradeTitle: `ワークスペースをダウングレードできません`,
                 downgradeSubTitle: `このワークスペースは、複数のカードフィードが接続されているため(Expensifyカードを除く)、ダウングレードできません。どうぞ <a href="#">カードフィードを1つだけ保持</a> 続行する。`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `${connection}にアカウントを追加し、再度接続を同期してください。`,
                 expensifyCardBannerTitle: 'Expensifyカードを取得する',
                 expensifyCardBannerSubtitle: 'すべての米国での購入でキャッシュバックを楽しみ、Expensifyの請求書が最大50%オフ、無制限のバーチャルカードなど、さらに多くの特典があります。',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 4fefcdcf..89530ad2 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -4817,7 +4817,6 @@ ${amount} voor ${merchant} - ${date}`,
                 defaultCard: 'Standaardkaart',
                 downgradeTitle: `Kan werkruimte niet downgraden`,
                 downgradeSubTitle: `Deze werkruimte kan niet worden gedowngraded omdat er meerdere kaartfeeds zijn verbonden (met uitzondering van Expensify Cards). Alstublieft <a href="#">houd slechts één kaartfeed</a> om door te gaan.`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `Voeg het account toe in ${connection} en synchroniseer de verbinding opnieuw.`,
                 expensifyCardBannerTitle: 'Verkrijg de Expensify Card',
                 expensifyCardBannerSubtitle: 'Geniet van cashback op elke aankoop in de VS, tot 50% korting op je Expensify-rekening, onbeperkte virtuele kaarten en nog veel meer.',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index c6c0dd6b..8a341d1f 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -4432,7 +4432,6 @@ ${amount} dla ${merchant} - ${date}`,
             displayedAsTagDescription: 'Dział będzie można wybrać dla każdego indywidualnego wydatku w raporcie pracownika.',
             displayedAsReportFieldDescription: 'Wybór działu będzie dotyczył wszystkich wydatków w raporcie pracownika.',
             toggleImportTitle: ({mappingTitle}: ToggleImportTitleParams) => `Wybierz, jak obsługiwać Sage Intacct <strong>${mappingTitle}</strong> w Expensify.`,
-
             expenseTypes: 'Typy wydatków',
             expenseTypesDescription: 'Twoje typy wydatków Sage Intacct zostaną zaimportowane do Expensify jako kategorie.',
             accountTypesDescription: 'Twój plan kont Sage Intacct zostanie zaimportowany do Expensify jako kategorie.',
@@ -4806,7 +4805,6 @@ ${amount} dla ${merchant} - ${date}`,
                 defaultCard: 'Domyślna karta',
                 downgradeTitle: `Nie można obniżyć poziomu workspace.`,
                 downgradeSubTitle: `Tego miejsca pracy nie można obniżyć, ponieważ jest połączonych wiele kanałów kart (z wyłączeniem kart Expensify). Proszę <a href="#">zachowaj tylko jeden kanał kart</a> aby kontynuować.`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `Proszę dodać konto w ${connection} i ponownie zsynchronizować połączenie.`,
                 expensifyCardBannerTitle: 'Zdobądź kartę Expensify',
                 expensifyCardBannerSubtitle:
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 31b648b0..676a1451 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -4431,7 +4431,6 @@ ${amount} para ${merchant} - ${date}`,
             displayedAsTagDescription: 'O departamento será selecionável para cada despesa individual no relatório de um funcionário.',
             displayedAsReportFieldDescription: 'A seleção de departamento será aplicada a todas as despesas no relatório de um funcionário.',
             toggleImportTitle: ({mappingTitle}: ToggleImportTitleParams) => `Escolha como lidar com o Sage Intacct <strong>${mappingTitle}</strong> in Expensify.`,
-
             expenseTypes: 'Tipos de despesas',
             expenseTypesDescription: 'Seus tipos de despesas do Sage Intacct serão importados para o Expensify como categorias.',
             accountTypesDescription: 'Seu plano de contas do Sage Intacct será importado para o Expensify como categorias.',
@@ -4807,7 +4806,6 @@ ${amount} para ${merchant} - ${date}`,
                 defaultCard: 'Cartão padrão',
                 downgradeTitle: `Não é possível rebaixar o espaço de trabalho`,
                 downgradeSubTitle: `Este espaço de trabalho não pode ser rebaixado porque vários feeds de cartão estão conectados (excluindo os Cartões Expensify). Por favor, <a href="#">manter apenas um feed de cartão</a> para prosseguir.`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `Por favor, adicione a conta em ${connection} e sincronize a conexão novamente.`,
                 expensifyCardBannerTitle: 'Obtenha o Cartão Expensify',
                 expensifyCardBannerSubtitle: 'Aproveite o cashback em todas as compras nos EUA, até 50% de desconto na sua fatura do Expensify, cartões virtuais ilimitados e muito mais.',
@@ -7381,7 +7379,6 @@ ${amount} para ${merchant} - ${date}`,
         exportInProgress: 'Exportação em andamento',
         conciergeWillSend: 'Concierge enviará o arquivo em breve.',
     },
-
     avatarPage: {
         title: 'Editar foto de perfil',
         upload: 'Carregar',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 31f4e8aa..c4604ffb 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -4717,7 +4717,6 @@ ${merchant}的${amount} - ${date}`,
                 defaultCard: '默认卡片',
                 downgradeTitle: `无法降级工作区`,
                 downgradeSubTitle: `由于连接了多个卡片馈送(不包括Expensify卡),此工作区无法降级。请 <a href="#">仅保留一个卡片信息流</a> 继续。`,
-
                 noAccountsFoundDescription: ({connection}: ConnectionParams) => `请在${connection}中添加账户并再次同步连接。`,
                 expensifyCardBannerTitle: '获取Expensify卡',
                 expensifyCardBannerSubtitle: '享受每笔美国消费的现金返还,Expensify账单最高可享50%折扣,无限虚拟卡等更多优惠。',

Note

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

@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

Unable to complete full review: The PR diff exceeded GitHub API limits (300+ files) and branch checkout was restricted. Based on the limited file analysis performed on accessible component files, no violations of the specified performance rules were detected in the reviewed subset. However, a comprehensive review of all 100+ changed files could not be completed due to technical constraints.

Recommendation: Please reduce PR size or enable direct branch access for thorough review.

@github-actions github-actions bot changed the title Stephanieelliott patch 16 [No QA] Stephanieelliott patch 16 Nov 7, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

HelpDot Documentation Review

Overall Assessment

This PR includes significant documentation updates across 12 files, with 502 additions focused primarily on New Expensify help articles. The changes include 4 new Concierge AI articles (502 new lines), updates to existing reports and expenses documentation, a new Uber for Business connection guide, and minor updates to routing configuration.

The documentation I was able to review demonstrates strong overall quality with clear, user-focused writing and good structural organization. However, there are some areas for improvement in consistency and AI readiness.

Scores Summary

  • Readability: 8/10 - Clear, accessible language with good use of formatting. Minor inconsistencies in heading styles and some lengthy sentences that could be simplified.
  • AI Readiness: 7/10 - Good YAML metadata and descriptive headings in most files, but some context gaps and inconsistent heading hierarchy usage.
  • Style Compliance: 8/10 - Generally follows Expensify voice with proper terminology. Some minor formatting inconsistencies and FAQ structure variations.

Key Findings

Strengths:

  • Excellent user-centric approach: All reviewed articles focus on practical user scenarios and workflows
  • Strong YAML metadata: Comprehensive title, description, and keywords in frontmatter
  • Good use of formatting: Effective use of bold, notes, warnings, and structured steps
  • Clear FAQs: Most articles include helpful FAQ sections addressing common questions
  • Comprehensive coverage: Articles cover multiple use cases and scenarios (e.g., client-based, project-based, monthly reporting)

Areas for Improvement:

  • Heading hierarchy inconsistency: Mix of single (#) and double (##) hashtags for top-level sections. HelpDot standards require consistent use of # for main sections and ## for subsections only
  • Context for AI: Some headings use vague pronouns ("How to retract or edit submitted reports") rather than more specific feature names that would help AI assistants understand context
  • Formatting variations: Some inconsistencies in note formatting and button label presentation
  • Cross-references: Limited use of helpful cross-references between related articles

Specific Observations

Create-and-Submit-Reports.md (139 lines):

  • Excellent structure with clear step-by-step instructions
  • Good use cases section showing real-world applications
  • Minor issue: Line 43 missing period at end of sentence
  • Copilot references are helpful and well-linked

Delete-Expenses.md (78 lines):

  • Clear distinction between different deletion scenarios
  • Good warning callouts (⚠️) for destructive actions
  • Well-structured FAQ addressing admin limitations

Edit-Expense-Reports.md (85 lines):

  • Concise and focused on the retraction workflow
  • Good modal warning explanation for accounting integrations
  • Clear status-based instructions (Processing vs Closed)

Commercial-feeds.md (133 lines):

  • Excellent technical detail for different card providers
  • Good use of external links and numbered steps
  • Images referenced but not visible in markdown review
  • Line 70: Numbering restarts incorrectly (should be 5, 6, 7 not 3, 4)

Edit-and-Submit-Expense-Reports.md (306 lines):

  • Comprehensive guide covering many workflows
  • Good platform-specific instructions (Desktop vs Mobile)
  • Report statuses section is particularly clear
  • Could benefit from more concise intro paragraphs

Recommendations

High Priority:

  1. Standardize heading hierarchy: Review all files to ensure # is used for main sections and ## for subsections only
  2. Fix numbering issues: Correct the step numbering in Commercial-feeds.md (line 70)
  3. Add missing punctuation: Fix incomplete sentence in Create-and-Submit-Reports.md (line 43)

Medium Priority:
4. Enhance AI readiness: Replace vague pronouns in headings with specific feature names (e.g., "Retract Submitted Reports in New Expensify" vs "How to retract or edit submitted reports")
5. Add breadcrumb context: Consider adding breadcrumb-style navigation context to YAML frontmatter
6. Standardize note formatting: Ensure consistent use of Note: vs plain Note formatting

Low Priority:
7. Cross-link related articles: Add more references between related help articles (e.g., link from Delete-Expenses to Edit-Expense-Reports)
8. Consider reading level: Some sentences could be simplified for broader accessibility

Files Reviewed

  • ✅ docs/articles/new-expensify/reports-and-expenses/Create-and-Submit-Reports.md - Good quality, minor punctuation fix needed
  • ✅ docs/articles/new-expensify/reports-and-expenses/Delete-Expenses.md - Strong, clear and comprehensive
  • ✅ docs/articles/new-expensify/reports-and-expenses/Edit-Expense-Reports.md - Good quality, concise and focused
  • ✅ docs/articles/new-expensify/connect-credit-cards/Commercial-feeds.md - Good technical detail, numbering issue to fix
  • ✅ docs/articles/expensify-classic/reports/Edit-and-Submit-Expense-Reports.md - Comprehensive, could be more concise
  • ✅ docs/_data/_routes.yml - Configuration file, no content issues
  • ⏭️ docs/articles/new-expensify/concierge-ai/* (4 new files) - Unable to review (new files not yet in working branch)
  • ⏭️ docs/articles/new-expensify/connections/Uber-for-Business.md - Unable to review (new file)
  • ⏭️ docs/new-expensify/hubs/concierge-ai/index.html - Unable to review (new file)

Overall Recommendation

Approve with minor revisions. The documentation demonstrates strong quality and user focus. The identified issues are primarily formatting and consistency improvements rather than fundamental content problems. The new Concierge AI content (which I couldn't fully review) represents significant added value. Once the numbering, punctuation, and heading hierarchy issues are addressed, this will be excellent documentation.


🤖 Review conducted by Claude Code Documentation Specialist

@@ -57,9 +57,9 @@ Company card expenses can’t be deleted if **Allow deleting transactions** is t

Expense actions like deleting, editing, or retracting can only be done in your own account. Even Workspace Admins can’t delete another member’s expenses. If you need to help a teammate, ask them to add you as a [Copilot](https://help.expensify.com/articles/new-expensify/settings/Copilot-Access) so you can assist from their account.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: Use "workspace" instead of "Workspace Admin" for consistency. Should be: "Even workspace admins can't delete another member's expenses."

You can retract reports with the following statuses:
- **Processing reports**: Only the submitter (or a Workspace Admin submitting their own report) can use **Undo submit**.
- **Closed reports**: Only **Workspace Admins** can use **Undo close**.
- **Outstanding reports**: Only the submitter (or a Workspace Admin submitting their own report) can use **Retract**.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: Use "workspace admin" (lowercase) instead of "Workspace Admin" for consistency with Expensify terminology standards.

- **Processing reports**: Only the submitter (or a Workspace Admin submitting their own report) can use **Undo submit**.
- **Closed reports**: Only **Workspace Admins** can use **Undo close**.
- **Outstanding reports**: Only the submitter (or a Workspace Admin submitting their own report) can use **Retract**.
- **Done reports**: Only **Workspace Admins** can use **Retract**.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: Use "workspace admin" (lowercase) consistently. Should be: "- Closed reports: Only workspace admins can use Undo close."

3. A system message confirms the report is retracted and editable.

**Note:** Only Workspace Admins can retract their own closed reports. Admins can’t retract other members’ reports unless they’ve been added as a [Copilot](https://help.expensify.com/articles/new-expensify/settings/Copilot-Access).
**Note:** Only Workspace Admins can retract done reports.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: Use "workspace admin" (lowercase) instead of "Workspace Admins".

- **Cancel**: Dismisses the warning message without making changes to the expense report.

Once reopened, a Workspace Admin can fully edit the report—adding or deleting expenses, changing categories, and more.
After retracting, a Workspace Admin can fully edit the report—adding or deleting expenses, changing categories, and more.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: Use "workspace admin" (lowercase). Should be: "Once reopened, a workspace admin can fully edit the report..."

- You can only retract reports you submitted from your own account. Reports submitted by other members require CoPilot access to retract.
3. Tap **Retract**.
4. The report will change to **Draft** and display a **Retracted** system message.
- You can only retract outstanding reports you submitted from your own account. Reports submitted by other members require CoPilot access to retract.
Copy link
Contributor

Choose a reason for hiding this comment

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

Terminology violation: "CoPilot" should be "Copilot" (capital P, no capital O). Should be: "Reports submitted by other members require Copilot access to retract."

@codecov
Copy link

codecov bot commented Nov 7, 2025

Codecov Report

❌ Patch coverage is 47.62349% with 562 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/components/Search/index.tsx 0.00% 88 Missing ⚠️
src/libs/actions/Link.ts 33.33% 48 Missing ⚠️
src/libs/actions/IOU.ts 51.94% 37 Missing ⚠️
...tView/MoneyRequestReportTransactionsNavigation.tsx 0.00% 31 Missing ⚠️
src/libs/Formula.ts 81.03% 22 Missing ⚠️
...nents/ReportActionItem/MoneyRequestReceiptView.tsx 0.00% 16 Missing ⚠️
...c/components/ReportActionItem/MoneyRequestView.tsx 0.00% 13 Missing ⚠️
src/components/Search/SearchList/index.tsx 0.00% 13 Missing ⚠️
src/libs/actions/Task.ts 0.00% 13 Missing ⚠️
src/libs/actions/Domain.ts 0.00% 12 Missing ⚠️
... and 80 more
Files with missing lines Coverage Δ
src/CONST/index.ts 85.71% <ø> (ø)
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/AddPaymentCard/PaymentCardForm.tsx 92.75% <100.00%> (ø)
src/components/AvatarWithDisplayName.tsx 83.82% <ø> (+1.47%) ⬆️
src/components/CategoryPicker.tsx 0.00% <ø> (ø)
src/components/DestinationPicker.tsx 5.55% <ø> (ø)
.../FloatingCameraButton/BaseFloatingCameraButton.tsx 85.00% <ø> (ø)
src/components/Form/FormProvider.tsx 56.31% <100.00%> (ø)
src/components/Form/InputWrapper.tsx 100.00% <ø> (ø)
... and 183 more

... and 128 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.49-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

1 similar comment
@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.49-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.52-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 cancelled 🔪
🤖 android 🤖 cancelled 🔪
🍎 iOS 🍎 failure ❌

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.2.54-1 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.2.52-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 cancelled 🔪
🤖 android 🤖 cancelled 🔪
🍎 iOS 🍎 failure ❌

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.