Merge branch 'Expensify:main' into fix-tax-detail-rhn-fallback-redirect

Author: allgandalf

.claude/scripts/createInlineComment.sh

@@ -47,11 +47,12 @@ readonly LINE_ARG="${3:-}"
 validate_rule "$BODY_ARG"
 echo "Comment approved: $COMMENT_STATUS_REASON"
 
-readonly FOOTER=$'\n\n---\n\nPlease rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.'
-readonly COMMENT_BODY="${BODY_ARG}${FOOTER}"
-
 COMMIT_ID=$(gh api "/repos/$GITHUB_REPOSITORY/pulls/$PR_NUMBER" --jq '.head.sha')
 readonly COMMIT_ID
+readonly SHORT_SHA="${COMMIT_ID:0:7}"
+
+readonly FOOTER=$'\n\n---\n\n'"Reviewed at: [${SHORT_SHA}](https://github.com/${GITHUB_REPOSITORY}/commit/${COMMIT_ID}) | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency."
+readonly COMMENT_BODY="${BODY_ARG}${FOOTER}"
 
 PAYLOAD=$(jq -n \
     --arg body "$COMMENT_BODY" \

.github/workflows/cherryPick.yml

@@ -34,9 +34,34 @@ concurrency:
   cancel-in-progress: false
 
 jobs:
+  validate:
+    runs-on: blacksmith-2vcpu-ubuntu-2404
+    steps:
+      - name: Validate pull request URL
+        if: ${{ inputs.PULL_REQUEST_URL != '' }}
+        run: |
+          REPO_FULL_NAME=$(echo '${{ inputs.PULL_REQUEST_URL }}' | sed -E 's|https?://github.com/([^/]+/[^/]+)/pull/.*|\1|')
+          if [[ "$REPO_FULL_NAME" != ${{ github.repository }} ]] && [[ ! "$REPO_FULL_NAME" =~ Expensify/Mobile-Expensify* ]]; then
+            echo "::error::❌ Cherry picks are only supported for the Expensify/App and Expensify/Mobile-Expensify repositories. Found: $REPO_FULL_NAME"
+            exit 1
+          fi
+
+      - name: Verify PR is merged
+        if: ${{ inputs.PULL_REQUEST_URL != '' }}
+        env:
+          GITHUB_TOKEN: ${{ secrets.OS_BOTIFY_TOKEN }}
+        run: |
+          if gh pr view "${{ inputs.PULL_REQUEST_URL }}" --json mergedAt | jq --exit-status '.mergedAt'; then
+            echo "PR is merged: ${{ inputs.PULL_REQUEST_URL }}"
+          else
+            echo "::error::❌ PR is not merged: ${{ inputs.PULL_REQUEST_URL }}"
+            exit 1
+          fi
+
   createNewVersion:
     uses: ./.github/workflows/createNewVersion.yml
     secrets: inherit
+    needs: [validate]
     with:
       # In order to submit a new build for production review, it must have a higher PATCH version than the previously-submitted build.
       # The typical case is that with each staging deploy, we bump the BUILD version, and with each prod deploy we bump the PATCH version.
@@ -59,14 +84,6 @@ jobs:
           echo "REPO_FULL_NAME=$(echo '${{ inputs.PULL_REQUEST_URL }}' | sed -E 's|https?://github.com/([^/]+/[^/]+)/pull/.*|\1|')" >> "$GITHUB_OUTPUT"
           echo "PR_NUMBER=$(echo '${{ inputs.PULL_REQUEST_URL }}' | sed -E 's|.*/pull/([0-9]+).*|\1|')" >> "$GITHUB_OUTPUT"
 
-      - name: Verify pull request URL
-        if: ${{ inputs.PULL_REQUEST_URL != '' }}
-        run: |
-          if [[ "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" != ${{ github.repository }} ]] && [[ ! "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" =~ Expensify/Mobile-Expensify* ]]; then
-            echo "::error::❌ Cherry picks are only supported for the Expensify/App and Expensify/Mobile-Expensify repositories. Found: ${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}"
-            exit 1
-          fi
-
       - name: Set conflict branch name
         if: ${{ inputs.PULL_REQUEST_URL != '' }}
         id: getBranchName

Mobile-Expensify

@@ -111,8 +111,8 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         multiDexEnabled rootProject.ext.multiDexEnabled
-        versionCode 1009035500
-        versionName "9.3.55-0"
+        versionCode 1009035701
+        versionName "9.3.57-1"
         // Supported language variants must be declared here to avoid from being removed during the compilation.
         // This also helps us to not include unnecessary language variants in the APK.
         resConfigs "en", "es"

android/app/build.gradle

@@ -702,7 +702,7 @@ A dynamic route is a URL suffix (e.g. `verify-account`) that can be appended to
 
 Do not use dynamic routes when:
 - Your use case falls under the [current limitations](#current-limitations-work-in-progress):
-  - You need path parameters in dynamic suffixes (e.g. `a/:reportID`).
+  - You need optional path parameters in dynamic suffixes (e.g. `a/:reportID?`).
 - The screen has a single, fixed entry and a fixed back destination. In this case, use a normal static route instead.
 
 ### Dynamic routes configuration
@@ -751,9 +751,9 @@ KEYBOARD_SHORTCUTS: {
 
 ### Current limitations (work in progress)
 
-- **Path parameters:** Suffixes must not include path params (e.g. `a/:reportID`). Query parameters are supported - see [Dynamic routes with query parameters](#dynamic-routes-with-query-parameters).
+- **Optional path parameters:** Suffixes must not include optional path params (e.g. `a/:reportID?`). Required path parameters (e.g. `flag/:reportActionID`) and query parameters are supported - see [Dynamic routes with query parameters](#dynamic-routes-with-query-parameters).
 
-If you try to use dynamic routes for this case now, you will either fail to navigate to the page at all or end up on a non-existent page, and the navigation will be broken.
+If you try to use dynamic routes with optional path parameters now, you will either fail to navigate to the page at all or end up on a non-existent page, and the navigation will be broken.
 
 ### Multi-segment dynamic routes
 
@@ -892,9 +892,7 @@ and [`src/pages/settings/Profile/PersonalDetails/DynamicCountrySelectionPage.tsx
 ### How to add a new dynamic route
 
 1. Add to `DYNAMIC_ROUTES` in [`src/ROUTES.ts`](../src/ROUTES.ts): define `path` and
-`entryScreens` (screen names that may open this route).
-If the suffix needs query parameters, also define `getRoute`
-and `queryParams` - see
+`entryScreens` (screen names that may open this route). If the suffix needs path parameters, define `path` with `:param` placeholders and a `getRoute` function. If the suffix needs query parameters, also define `getRoute` and `queryParams` - see
 [Dynamic routes with query parameters](#dynamic-routes-with-query-parameters).
 2. Add a screen constant in [`src/SCREENS.ts`](../src/SCREENS.ts).
 The name must start with the `DYNAMIC_` prefix

assets/images/camera-flip.svg

@@ -554,6 +554,7 @@
         "picklists",
         "PINATM",
         "PINGPONG",
+        "PINATM",
         "pkill",
         "Pluginfile",
         "pluralrules",

contributingGuides/NAVIGATION.md

@@ -15,7 +15,7 @@ defaults:
       layout: "default"
       image: /assets/images/og-preview-image.png
 
-exclude: [README.md, TEMPLATE.md, vendor]
+exclude: [README.md, TEMPLATE.md, vendor, Gemfile, Gemfile.lock]
 
 plugins:
   - jekyll-seo-tag

cspell.json

@@ -0,0 +1,51 @@
+---
+title: Assign Company Cards
+description: Learn how to assign company cards to members in your Workspace using the Company cards page.
+keywords: [New Expensify, assign company cards, Expensify card assignment, workspace company cards, assign card to employee]
+internalScope: Audience is Workspace Admins. Covers assigning company cards to members in New Expensify, does not cover initial connection or troubleshooting connection issues. 
+---
+
+# Assign Company Cards
+
+Assigning company cards links company cards to Workspace members so their transactions are automatically imported into their account for expense tracking.
+
+---
+
+## Who can assign company cards 
+
+Workspace Admins can assign company cards after a company card feed is connected.
+
+If you haven’t set up a feed yet, learn how to set one up:
+
+ - [Learn how to set up a direct company card feed connection](/articles/new-expensify/connect-credit-cards/Set-up-a-Direct-Company-Card-Feed-Connection).
+ - [Learn how to set up a commercial card feed connection](/articles/new-expensify/connect-credit-cards/Set-up-a-Commercial-Card-Feed-Connection). 
+
+## How to assign company cards 
+
+1. Click the navigation tabs (on the left on web, on the bottom on mobile) and select **Workspaces > [Workspace Name]**.
+2. Select **Company cards**.
+3. Select the card connection name. 
+4. Click **Assign card** on the card you want to assign. 
+5. Enter the assignee's name, email address, or phone number. 
+6. Review the details and click **Assign card** to finalize the assignment.
+
+---
+
+## What happens after you assign company cards
+
+ - Posted transactions from the assigned card import automatically into the member's account as expenses.
+ - The imported company card expenses are added to reports and submitted according to Workspace rules.
+
+# FAQ
+
+## Can I assign a company card to someone who is not a member of the Workspace? 
+
+You can enter any name, email address, or phone number when assigning a company card. However, only Workspace members can have company cards assigned to them. If the assignee is not yet a Workspace member, you can invite them while assigning the card. 
+
+## Can I assign multiple company cards to one member?
+
+Yes. A member can have multiple company cards assigned. Each card’s transactions will be automatically imported into their account.
+
+## Can members unassign their own company cards?
+
+No. Only Workspace Admins can assign or reassign company cards.