[No QA] Add redirect for split personal expenses article

[garrettmknight]

Adding redirect for Personal Expense Split since I'm removing the help page.

#80563

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

[melvin-bot]

@aldo-expensify 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]

NOTE: It looks like docs/redirects.csv was modified in this PR. Please see this SO for special instructions on how to review changes to that file.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a single redirect entry to properly handle the deletion of the standalone "Split Personal Expenses" article (from PR #80563). The redirect correctly points users from the old standalone article URL to the consolidated "Split Personal Expenses" section within the "Create an Expense" article. This is a clean consolidation effort that improves documentation structure by reducing redundancy.

Scores Summary

• Readability: 10/10 - The redirect entry follows the established CSV format perfectly and is immediately understandable.
• AI Readiness: 10/10 - The target section in Create-an-Expense.md has a clear heading ("Split Personal Expenses") and provides complete, self-contained instructions with proper context.
• Style Compliance: 10/10 - The redirect follows the exact formatting pattern used throughout the redirects.csv file, maintaining consistency with hundreds of existing entries.

Key Findings

Positive Aspects:

• The redirect URL structure is correct and uses the proper anchor format (#split-personal-expenses)
• The target content in Create-an-Expense.md is well-structured with clear step-by-step instructions
• The consolidation makes logical sense - splitting expenses is part of the expense creation workflow
• The target section maintains all the key information from the original standalone article
• Proper heading hierarchy is maintained in the target document (using # and ##)

Technical Validation:

• Target URL anchor (#split-personal-expenses) correctly matches the "Split Personal Expenses" heading in Create-an-Expense.md
• The redirect format matches the established pattern: old-url,new-url#anchor
• No trailing commas or formatting issues present

Recommendations

Immediate Actions:

1. Verify SEO implications - Ensure the redirect is implemented server-side with proper 301 status codes
2. Update any internal links - Search the codebase for any hardcoded references to the old Split-Personal-Expenses article URL
3. Monitor broken links - After deployment, verify that the redirect functions correctly on all platforms

Optional Improvements:

• Consider adding a note in the FAQ section of Create-an-Expense.md that explicitly mentions this article consolidation (for users who may have bookmarked the old URL)

Files Reviewed

• docs/redirects.csv - New redirect entry added correctly at line 901. Format is consistent, target URL is valid, and the change supports documentation consolidation efforts.

Conclusion

This is a straightforward, well-executed redirect that supports documentation maintenance. The change is low-risk and follows best practices for handling deleted content. The target section provides comprehensive coverage of the split expenses feature, making this consolidation beneficial for users.

Status: Approved - This redirect change is ready to merge once the related deletion PR (#80563) is also approved.

[OSBotify]

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

[aldo-expensify]

All yours @stephanieelliott

[melvin-bot]

@stephanieelliott looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[aldo-expensify]

Removing Emergency label since we just missed the checklist which doesn't apply here since we are just updating some redirections in the help docs

[OSBotify]

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

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

[OSBotify]

🚀 Deployed to production by https://github.com/roryabraham in version: 9.3.10-6 🚀

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