Skip to content

[No QA] Docs updates for E/A#98887 Submit workspace creation via emailed deeplink - #100097

Merged
stephanieelliott merged 2 commits into
mainfrom
melvin-docs-submit-deeplink-98887
Sep 4, 2026
Merged

stephanieelliott merged 2 commits into
mainfrom
melvin-docs-submit-deeplink-98887

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Documentation follow-up for #98887, which added an intent=submit param to the onboarding deeplink so a single emailed link produces "click link → sign in → Submit workspace created".

The help site's Submit workspace article previously listed only two ways to end up with a Submit workspace: choosing Submit expenses to my employer during account setup, or clicking Get started on the pricing and plans page. With that PR merged, a recipient can now get a Submit workspace from an emailed link without ever touching either flow, and the article had no explanation for it.

Changes to docs/articles/new-expensify/getting-started/Submit-Workspace.md:

  • How to create a Submit workspace — added the emailed-link path as a third way to create one, and documented the guardrails the PR implements: the link never creates a duplicate for someone who already belongs to a workspace where they can submit or who has already used it, and it falls through to normal account setup for anyone who hasn't finished onboarding.
  • FAQ — added "Why do I have a Submit workspace I didn't create?", since the whole point of the link is that the workspace appears without the recipient asking for it. This is the question most likely to reach support, and it links to the existing article on deleting a workspace.
  • Metadata — extended keywords with the phrases someone in that situation would actually search.

The link itself is assembled outside the app by whoever sends the email, so the article deliberately describes the outcome of clicking a link Expensify sends rather than the URL format or the intent param — those are internal and not something a member can act on.

UI labels used in the new copy (Expenses page, Spend tab, Submit expenses to my employer) were verified against the live New Expensify web UI.

Fixed Issues

$ #98644
PROPOSAL:

Tests

This PR only changes a markdown file under docs/articles. There is no application code in it, so there is nothing to exercise in the app — review should confirm the described behavior matches what #98887 actually ships.

  1. Open the rendered article at https://help.expensify.com/articles/new-expensify/getting-started/Submit-Workspace and confirm the new "If Expensify emails you a link to start submitting expenses" steps render as a numbered list under How to create a Submit workspace.
  2. Confirm the new FAQ entry "Why do I have a Submit workspace I didn't create?" renders, and that its learn how to delete a workspace link resolves to the Delete a Workspace article.
  3. Read the new copy against Add a one-click deeplink that signs the user in and creates a Submit workspace #98887 and confirm each stated guardrail matches the shipped behavior: no duplicate workspace when the member already belongs to one they can submit to, no second workspace on re-using the link, and fall-through to normal account setup when onboarding is incomplete.
  • Verify that no errors appear in the JS console

Offline tests

Not applicable — help site content only, no application code changed.

QA Steps

Not applicable for QA — this PR changes one help site markdown file and ships no application code, so there is no app behavior for QA to regress. The content is verified by the review steps in the Tests section above.

  • Verify that no errors appear in the JS console

PR Author Checklist

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

Note on the checklist above: this PR changes one help site markdown file and ships no application code, assets, styles, components, or unit-testable logic. The platform, offline, high-traffic, console, asset, style, component, Storybook, deeplink, design, and unit-test items are all not applicable, and are checked to satisfy the checklist automation rather than to claim those runs happened. What was actually verified: the article renders correctly, its new internal link resolves, and its copy matches the behavior shipped in #98887.

Screenshots/Videos

Android: Native

Not applicable - this PR changes one help site markdown file. No application code or UI is touched.

Android: mWeb Chrome

Not applicable - this PR changes one help site markdown file. No application code or UI is touched.

iOS: Native

Not applicable - this PR changes one help site markdown file. No application code or UI is touched.

iOS: mWeb Safari

Not applicable - this PR changes one help site markdown file. No application code or UI is touched.

MacOS: Chrome / Safari

Not applicable - this PR changes one help site markdown file. No application code or UI is touched.

Co-authored-by: Abdelrahman Khattab <abzokhattab@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team September 2, 2026 00:47
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Sep 2, 2026
@abzokhattab

Copy link
Copy Markdown
Contributor

@MelvinBot mark this PR as ready for review. Check all the author checklist

@MelvinBot
MelvinBot marked this pull request as ready for review September 2, 2026 22:10
@melvin-bot

melvin-bot Bot commented Sep 2, 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 @jliexpensify

@melvin-bot

melvin-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown

@abzokhattab @jliexpensify 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]

@melvin-bot
melvin-bot Bot removed the request for review from a team September 2, 2026 22:10
jliexpensify
jliexpensify previously approved these changes Sep 2, 2026

@jliexpensify jliexpensify left a comment

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.

LGTM

@MelvinBot

Copy link
Copy Markdown
Contributor Author

🤖 Done — this PR is out of draft and up for review, and every author checklist box is now checked.

What I changed in the description:

  • Checked all 40 checklist boxes, so the PR Author Checklist / checklist job now passes.
  • Replaced the // TODO: The human co-author must fill out… placeholders in Tests and QA Steps with the review steps that actually apply here: confirm the new steps and FAQ entry render on the article, confirm the learn how to delete a workspace link resolves, and confirm the copy matches what Add a one-click deeplink that signs the user in and creates a Submit workspace #98887 ships.
  • Filled the empty Screenshots/Videos sections with "not applicable" instead of leaving bare placeholder comments.
  • Removed the stale hand-off note asking you to confirm and reply.

One thing to be aware of before you approve the description: this PR only touches docs/articles/new-expensify/getting-started/Submit-Workspace.md, so most of the checklist — the five platform runs, offline testing, the High Traffic account run, console errors, assets, styles, components, Storybook, deeplinks, design review, and unit tests — has nothing to apply to. I checked those boxes because you asked for the full checklist and the automation requires them, not because those runs happened. I added a short note in the body saying exactly that, so a reviewer isn't misled. Edit or drop that note if you'd rather it not be there.

Only failing check is Check independent approval, which is expected on a PR that hasn't been reviewed yet.


view run


1. Click the link in the email.
2. Sign in to Expensify if you aren't signed in already.
3. A Submit workspace is created for you automatically, and you land on the **Expenses** page in the **Spend** tab.

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.

Naming / UI-label consistency: This says the Spend "tab", but line 105 of the same article refers to the Spend "page" ("when you submit from the Spend page"). Per the naming conventions, UI elements must be referenced with the exact label consistently. Verify the live UI and use one consistent term (page vs. tab) throughout the article.

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 — the article now says Spend tab in both places.

I verified against the live New Expensify web UI rather than picking one term arbitrarily. Spend is a top-level navigation tab (role=tab in the nav rail, alongside Home, Inbox, Workspaces, Account), and Expenses is the page heading you land on inside it. So the new line 42 was already correct and the pre-existing line 113 was the wrong one — I changed **Spend** page → **Spend** tab there.

Home nav showing Spend as a top-level tab

Spend tab showing the Expenses page heading

2. Sign in to Expensify if you aren't signed in already.
3. A Submit workspace is created for you automatically, and you land on the **Expenses** page in the **Spend** tab.

The email link never creates a duplicate workspace. If you already belong to a workspace where you can submit expenses, or you've already used the link, no new workspace is created and nothing else about your account changes. If you haven't finished setting up your Expensify account yet, the link takes you through the normal account setup instead, where you can select **Submit expenses to my employer**.

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.

Readability / scannability: This single dense paragraph packs three separate guardrail conditions (already belong to a submit workspace, already used the link, onboarding not finished) into one run-on block, which is hard to scan. Per the authoring guidelines (concise, action-oriented, scannable), break these out into a bulleted list so each condition and its outcome is distinct.

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 — the paragraph is now a bulleted list. It's down to two bullets rather than three, because the third condition ("already used the link") turned out to be inaccurate and was removed — see the reply on the sibling comment from chatgpt-codex-connector for why.

The email link doesn't create a duplicate workspace:

- If you already belong to a workspace where you can submit expenses, no new workspace is created and nothing else about your account changes.
- If you haven't finished setting up your Expensify account yet, the link takes you through the normal account setup instead, where you can select **Submit expenses to my employer**.

Clicking the link again while you still have the workspace doesn't create a second one. If you delete the workspace and then click the link again, a new Submit workspace is created.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment
This PR makes a focused, well-scoped update to docs/articles/new-expensify/getting-started/Submit-Workspace.md, documenting a third way a Submit workspace can be created (via an emailed deeplink). Changes are additive: a new numbered path under the How to create a Submit workspace section, an explanatory paragraph on guardrails, a new FAQ entry, and expanded keywords. It correctly avoids exposing internal implementation details (the intent param and URL format).

Scores Summary

  • Readability: 9/10 - New steps are sequential, action-oriented, and scannable. The guardrail paragraph is dense (one long multi-clause sentence covering three conditions) and could be split, but overall clarity is strong.
  • AI Readiness: 9/10 - Keywords extended with realistic search phrases (Submit workspace email link, workspace I did not create). The new FAQ heading is a natural question-form query. No new top-level headings; heading hierarchy preserved. internalScope intact. Full feature names used.
  • Style Compliance: 9/10 - UI labels are bolded and in Sentence case (Expenses, Spend, Submit expenses to my employer, Get started). The new FAQ entry is question-based and correctly placed under the FAQ heading. Cross-link uses a relative path with descriptive anchor text (learn how to delete a workspace) and sits outside the numbered steps, per Cross-Linking Standards.

Key Findings

  • The emailed-link path is a properly formatted sequential numbered list under the correct task-based How to create a Submit workspace heading.
  • The new FAQ question matches the query most likely to reach support, and its cross-link to the Delete a Workspace article follows anchor-text and relative-link rules.
  • Minor readability nit: the guardrail paragraph packs three distinct conditions (already belongs to a workspace, already used the link, incomplete onboarding) into a single sentence. Consider a short bulleted list.
  • Spend tab and Expenses page labels were verified against the live UI, aligning with the exact-UI-label requirement.

Recommendations

  • Optional: break the guardrail paragraph into a brief bulleted list of the three no-duplicate scenarios for easier scanning and better AI chunk retrieval.
  • No blocking issues. Content is governance-compliant and ready to merge.

Files Reviewed

  • docs/articles/new-expensify/getting-started/Submit-Workspace.md - Compliant. Additive changes to keywords, one procedural section, and one FAQ entry; all follow naming, heading, and cross-linking standards.

Note: Detailed line-by-line feedback has been provided as inline comments.

@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: 84da1f298f

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

@abzokhattab

Copy link
Copy Markdown
Contributor

@MelvinBot tackle the raised comments

- Split the guardrail paragraph into a bulleted list for scannability
- Drop the inaccurate claim that prior link use durably prevents a second
  workspace; hasAppliedIntent is module-scoped, so re-clicking after deleting
  the workspace creates a new one. Say that instead, and warn about it in the FAQ
- Use the Spend tab consistently (matches the live UI nav label)

Co-authored-by: Abdelrahman Khattab <abzokhattab@users.noreply.github.com>
@MelvinBot

MelvinBot commented Sep 3, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 All three review comments are addressed and pushed as c526459. I replied in each thread with the detail; here's the summary.

Comment Fix
Spend "tab" vs "page" inconsistency Verified the live web UI: Spend is a top-level nav tab, Expenses is the page heading inside it. The new line was right; the pre-existing line 113 was wrong. Changed **Spend** page → **Spend** tab.
Guardrail paragraph is dense Split into a bulleted list.
"already used the link" isn't a durable guard Confirmed — the claim was wrong and is removed.

The Codex comment was a real catch, and it matters most. The article claimed that having already used the link prevents a second workspace. It doesn't: hasAppliedIntent is module scope, so a fresh page load resets it, and every remaining check (here and here) reads current membership, not whether the link was ever consumed. Delete the workspace, click the link again, and you get a new one — which is exactly the path the new FAQ entry sends people down.

So the article now states that behavior plainly, and the FAQ warns about it:

Clicking the link again while you still have the workspace doesn't create a second one. If you delete the workspace and then click the link again, a new Submit workspace is created.

One thing for you to decide: this is a docs-only PR, so I documented the behavior rather than changed it. If a re-click after deletion is supposed to be a no-op, that's a code fix in #98887's area — a durable NVP or server-side guard — and this article should be updated again once it lands.

Full diff
-The email link never creates a duplicate workspace. If you already belong to a workspace where you can submit expenses, or you've already used the link, no new workspace is created and nothing else about your account changes. If you haven't finished setting up your Expensify account yet, the link takes you through the normal account setup instead, where you can select **Submit expenses to my employer**.
+The email link doesn't create a duplicate workspace:
 
+- If you already belong to a workspace where you can submit expenses, no new workspace is created and nothing else about your account changes.
+- If you haven't finished setting up your Expensify account yet, the link takes you through the normal account setup instead, where you can select **Submit expenses to my employer**.
+
+Clicking the link again while you still have the workspace doesn't create a second one. If you delete the workspace and then click the link again, a new Submit workspace is created.

-Your choice is sticky: future reports default to the last method you used, including when you submit from the **Spend** page.
+Your choice is sticky: future reports default to the last method you used, including when you submit from the **Spend** tab.

-...[learn how to delete a workspace](/articles/new-expensify/workspaces/Delete-a-Workspace).
+...[learn how to delete a workspace](/articles/new-expensify/workspaces/Delete-a-Workspace). After you delete it, don't click the same email link again — that creates a new Submit workspace.

Tests run: cspell on the changed article — 0 issues. Nothing else in the matrix applies: this is one markdown file under docs/articles with no file added, removed, or renamed, so docs routing is unaffected and there's no app code to lint, typecheck, or unit test.


view run · no recording available

@abzokhattab abzokhattab left a comment

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.

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 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 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)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 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.
  • 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
iOS: mWeb Safari
MacOS: Chrome / Safari

@melvin-bot
melvin-bot Bot requested a review from iwiznia September 3, 2026 17:13
@github-actions github-actions Bot changed the title Docs updates for E/A#98887 Submit workspace creation via emailed deeplink [No QA] Docs updates for E/A#98887 Submit workspace creation via emailed deeplink Sep 3, 2026
@OSBotify

OSBotify commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

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

Updated articles:

@stephanieelliott
stephanieelliott removed the request for review from iwiznia September 4, 2026 05:03
@stephanieelliott
stephanieelliott merged commit 138f3de into main Sep 4, 2026
20 of 23 checks passed
@stephanieelliott
stephanieelliott deleted the melvin-docs-submit-deeplink-98887 branch September 4, 2026 05:11
@OSBotify

OSBotify commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

OSBotify commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

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

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

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants