Skip to content

[No QA] Merging main on help article PR#84316

Closed
joekaufmanexpensify wants to merge 10000 commits intoVictoriaExpensify-patch-5from
main
Closed

[No QA] Merging main on help article PR#84316
joekaufmanexpensify wants to merge 10000 commits intoVictoriaExpensify-patch-5from
main

Conversation

@joekaufmanexpensify
Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify commented Mar 5, 2026

Explanation of Change

Merging Main on help article PR per this

Fixed Issues

$ https://expensify.slack.com/archives/C02QSAC6BJ8/p1772739499004489?thread_ts=1772561578.595719&cid=C02QSAC6BJ8

QA Steps

N/A

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 / Chrome
    • iOS / native
    • iOS / 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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 verified the translation was requested/reviewed 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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.js 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 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • 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(themeColors.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 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.
  • 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 author checklist, including those that don't apply to this PR.

sosek108 and others added 30 commits March 4, 2026 10:06
…ection

[No QA] Help site updates for change accounting section into multiple sections
…mportMemberFields

Co-authored-by: truph01 <truph01@users.noreply.github.com>
[NoQA] Implement the freeze and unfreeze options for admins
…-page-filter-inconsistencies-and-clean-up

# Conflicts:
#	src/components/Search/SearchPageHeader/SearchFiltersBar.tsx
#	tests/unit/Search/SearchUIUtilsTest.ts
…-empty-states

# Conflicts:
#	src/components/EmptyStateComponent/index.tsx
#	src/components/EmptyStateComponent/types.ts
#	src/pages/Search/EmptySearchView.tsx
#	src/pages/TransactionMerge/MergeTransactionsListContent.tsx
#	src/pages/workspace/companyCards/WorkspaceCompanyCardsFeedAddedEmptyPage.tsx
#	src/pages/workspace/companyCards/WorkspaceCompanyCardsFeedPendingPage.tsx
#	src/pages/workspace/expensifyCard/EmptyCardView.tsx
…-page-filter-inconsistencies-and-clean-up
…-fork into Guccio163/onyx-connect/policy_tags/duplicateExpenseTransaction
…-message-frontend

Send bespoke welcome message optimistically from frontend
[No QA] fix: PR Reviewer Checklist fails if more than 1 comment contains # Reviewer Checklist text
roryabraham and others added 18 commits March 5, 2026 10:31
…sed-disable-directives

Revert "[No QA] Remove unused eslint-disable directives"
…onnect/policy_tags/duplicateExpenseTransaction

Remove Onyx.connect() for the key: ONYXKEYS.COLLECTION.POLICY_TAGS from duplicateExpenseTransaction function
fix:78356: Back button on Validate your bank account page does nothing
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…e-time-typeguard-safety

Fix (telemetry): guard __moduleInitTimes access to prevent ReferenceError
Optimize getSections performance in SearchUIUtils
fix: Expensify card - The Choose a limit type page re-appears briefly
…ders

[No QA] Integrations Error Revamp: Create folders for integration troubleshooting docs
fix: send custom unit ids for distance rate and per-diem custom units
…nt-exact-match

[CP both] Fix subscription payment history not showing bills after merchant exact match change
Revert "Migrate `useBeforeRemove` to `usePreventRemove`  in `DiscardChangesConfirmation`"
fix: remove feature name from PublicDomainErrorPage
@joekaufmanexpensify joekaufmanexpensify requested review from a team and tgolen as code owners March 5, 2026 19:42
@melvin-bot melvin-bot bot requested review from inimaga and removed request for a team March 5, 2026 19:42
@melvin-bot
Copy link

melvin-bot bot commented Mar 5, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

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

Updated articles:

@codecov
Copy link

codecov bot commented Mar 5, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/CONFIG.ts 83.87% <ø> (ø)
src/CONST/index.ts 94.30% <100.00%> (+1.74%) ⬆️
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/components/Accordion/index.native.tsx 92.30% <100.00%> (+0.64%) ⬆️
src/components/AddPaymentMethodMenu.tsx 100.00% <100.00%> (+100.00%) ⬆️
src/components/AddUnreportedExpenseFooter.tsx 0.00% <ø> (ø)
src/components/AmountForm.tsx 0.00% <ø> (ø)
src/components/ApproverSelectionList.tsx 0.00% <ø> (ø)
src/components/AvatarWithDisplayName.tsx 83.82% <100.00%> (+0.74%) ⬆️
... and 91 more
... and 470 files with indirect coverage changes

@github-actions github-actions bot changed the title Merging main on help article PR [No QA] Merging main on help article PR Mar 5, 2026
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

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: 9d50c7ad70

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

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +109 to +112
core.warning(`PR #${prNumber} diff is too large for the GitHub API. Skipping incremental change detection.`);
core.setOutput('CHANGED_FILES', JSON.stringify([]));
core.setOutput('HAS_CHANGES', false);
return;

Choose a reason for hiding this comment

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

P2 Badge Fall back to local changes when PR diff is too large

When getPullRequestDiff() returns too_large, this branch sets HAS_CHANGES to false and exits, even though localChangedFiles already proved files changed in the pushed range. In generateTranslations.yml, all translation steps are gated on steps.check-en-changes.outputs.HAS_CHANGES == 'true', so large PRs that modify src/languages/en.ts will incorrectly skip translation generation entirely. Instead of reporting no changes, this path should use the local diff as a fallback (or fail loudly) so real updates are not dropped.

Useful? React with 👍 / 👎.

// eslint-disable-next-line @typescript-eslint/naming-convention
workflow_id: workflowID,
// eslint-disable-next-line @typescript-eslint/naming-convention
per_page: queueLimit,

Choose a reason for hiding this comment

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

P2 Badge Paginate workflow runs before deciding the queue is empty

This check only requests the most recent queueLimit runs and then filters by id < currentRunID; if more than queueLimit newer runs exist, older active runs fall off the first page and the action can incorrectly proceed while earlier runs are still in progress. In high-traffic periods this breaks the FIFO guarantee advertised by the action and allows out-of-order execution of testBuildOnPush runs.

Useful? React with 👍 / 👎.

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.