[No QA] docs: Add help site docs for Assign new cards feature by MelvinBot · Pull Request #86531 · Expensify/App

MelvinBot · 2026-03-27T12:56:03Z

Summary

Updates Company-Card-Settings.md to document the new Assign new cards option available on the feed settings page for direct feeds
Updates Direct-feeds.md with a new FAQ explaining why newly issued cards don't appear and how to refresh the card list

These changes reflect the new feature added in #86032, which allows workspace admins to re-authenticate with their bank to refresh the card list for direct feeds.

Test plan

Verify the rendered help articles display correctly on the help site
Verify the steps accurately describe the "Assign new cards" flow
Confirm the FAQ wording matches the actual product behavior

Update Company-Card-Settings.md and Direct-feeds.md to document the new Assign new cards option for direct card feeds, which allows workspace admins to refresh the card list by re-authenticating with their bank. Co-authored-by: Fedi Rajhi <[email protected]>

MelvinBot · 2026-03-27T12:58:27Z

The failing review check is unrelated to this PR's changes.

Analysis: The review check is a Claude Code review bot that crashed with an internal SDK execution error (Claude Code process exited with code 1). This is an infrastructure issue with the review action itself, not a problem with the documentation changes in this PR.

Evidence: The PR only modifies help site documentation files, while the failure is in the Claude Code Action SDK initialization/execution layer. Re-running the check should resolve this.

MelvinBot · 2026-03-27T12:58:35Z

I have failed to help you. I let you down and for that I am sorry. Please try again later. This may be due to a Claude outage (check here).

Failure details: https://github.com/Expensify/Expensify/actions/runs/23647276457

OSBotify · 2026-03-27T13:00:28Z

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

Updated articles:

stephanieelliott · 2026-04-03T04:09:59Z

@MelvinBot why can't I merge this pull request?

MelvinBot · 2026-04-03T04:11:36Z

All CI checks are passing. The PR is blocked because it requires an approving review (reviewDecision: REVIEW_REQUIRED). Once a reviewer approves it, the merge should unblock.

stephanieelliott · 2026-04-03T07:01:00Z

@MelvinBot I have write access to this repo, I should be able to merge .MD files under the path docs/articles. Why am I not able to merge this PR?

MelvinBot · 2026-04-03T07:02:35Z

Your approval satisfies the docs/articles/ @stephanieelliott CODEOWNERS rule, but the repo also has a wildcard rule (* @Expensify/pullerbear) that requires a review from the @Expensify/pullerbear team on every PR. That second required review is what's blocking the merge.

You'll need someone from @Expensify/pullerbear to approve as well.

melvin-bot · 2026-04-03T07:22:47Z

melvin-bot · 2026-04-03T07:22:50Z

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

kadiealexander · 2026-04-15T02:17:10Z

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
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

kadiealexander · 2026-04-15T02:20:19Z

@copilot resolve the merge conflicts in this pull request

fedirjh · 2026-04-15T02:36:37Z

@MelvinBot resolve the merge conflicts in this pull request

Resolve merge conflicts: - Configure-Company-Card-Settings.md: integrate "Assign new cards" bullet into main's updated formatting - Direct-feeds.md was renamed to Set-up-a-Direct-Company-Card-Feed-Connection.md on main; accept deletion and add the new FAQ to the renamed file Co-authored-by: Fedi Rajhi <[email protected]>

MelvinBot · 2026-04-15T02:43:25Z

Merge conflicts resolved. Here's what was done:

Configure-Company-Card-Settings.md — The file was renamed from Company-Card-Settings.md on main and its content was reformatted. Integrated the new Assign new cards bullet point into main's updated formatting style.
Direct-feeds.md — This file was renamed to Set-up-a-Direct-Company-Card-Feed-Connection.md on main. Accepted the deletion and added the new FAQ ("Why don't newly issued cards appear in the assignment list?") to the renamed file instead.

OSBotify · 2026-04-16T03:55:32Z

🚀 Deployed to staging by https://github.com/kadiealexander in version: 9.3.60-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot requested a review from stephanieelliott as a code owner March 27, 2026 12:56

MelvinBot assigned fedirjh Mar 27, 2026

MelvinBot mentioned this pull request Mar 27, 2026

Add Assign new cards option for direct card feeds v2 #86032

Merged

52 tasks

github-actions bot changed the title ~~docs: Add help site docs for Assign new cards feature~~ [No QA] docs: Add help site docs for Assign new cards feature Mar 27, 2026

Update Company-Card-Settings.md

d56fab2

stephanieelliott previously approved these changes Apr 3, 2026

View reviewed changes

stephanieelliott requested a review from a team April 3, 2026 07:22

melvin-bot bot requested review from kadiealexander and removed request for a team April 3, 2026 07:22

kadiealexander previously approved these changes Apr 15, 2026

View reviewed changes

MelvinBot dismissed stale reviews from kadiealexander and stephanieelliott via 9ca819c April 15, 2026 02:43

kadiealexander approved these changes Apr 15, 2026

View reviewed changes

kadiealexander merged commit 594cc71 into main Apr 15, 2026
20 checks passed

kadiealexander deleted the claude-helpsite-assignNewCards branch April 15, 2026 02:54

OSBotify mentioned this pull request Apr 16, 2026

Deploy Checklist: New Expensify 2026-04-16 #88022

Open

Conversation

MelvinBot commented Mar 27, 2026

Summary

Test plan

Uh oh!

MelvinBot commented Mar 27, 2026

Uh oh!

MelvinBot commented Mar 27, 2026

Uh oh!

OSBotify commented Mar 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

stephanieelliott commented Apr 3, 2026

Uh oh!

MelvinBot commented Apr 3, 2026

Uh oh!

stephanieelliott commented Apr 3, 2026

Uh oh!

MelvinBot commented Apr 3, 2026

Uh oh!

melvin-bot bot commented Apr 3, 2026 • edited by kadiealexander Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Concierge reviewer checklist:

Uh oh!

melvin-bot bot commented Apr 3, 2026

Uh oh!

kadiealexander commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

kadiealexander commented Apr 15, 2026

Uh oh!

fedirjh commented Apr 15, 2026

Uh oh!

MelvinBot commented Apr 15, 2026

Uh oh!

Uh oh!

OSBotify commented Apr 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

OSBotify commented Mar 27, 2026 •

edited

Loading

melvin-bot bot commented Apr 3, 2026 •

edited by kadiealexander

Loading

kadiealexander commented Apr 15, 2026 •

edited

Loading