Skip to content

[Payment due @mkhutornyi] Fix empty Account Manager banner#88611

Merged
Valforte merged 3 commits intomainfrom
valforte/fixAccountManagerBanner
Apr 27, 2026
Merged

[Payment due @mkhutornyi] Fix empty Account Manager banner#88611
Valforte merged 3 commits intomainfrom
valforte/fixAccountManagerBanner

Conversation

@Valforte
Copy link
Copy Markdown
Contributor

@Valforte Valforte commented Apr 23, 2026

Explanation of Change

Fix the empty Account Manager banner by getting the accountManagerAccountID from the account Onyx key, which is always filled by OpenApp and ReconnectApp, thus avoiding a race condiction when the Account Manager Report hasn't been yet loaded into Onyx.
While at it fixed the same problem in AccountManagerLinkRenderer and WorkspaceWorkflowsPage

Fixed Issues

#88539
PROPOSAL:

Tests

On a workspace with an Account Manager

  1. Open concierge by clicking on the persistent button in New Expensify
  2. The RHP should have a banner at the top of the chat suggesting the customer can reach out to their Account Manager
  3. Verify the banner is NOT empty
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

On a workspace with an Account Manager

  1. Open concierge by clicking on the persistent button in New Expensify
  2. The RHP should have a banner at the top of the chat suggesting the customer can reach out to their Account Manager
  3. Verify the banner is NOT empty
  • 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 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.
  • I verified that similar component doesn't exist in the codebase
  • I verified that all props are defined accurately and each prop has a /** comment above it */
  • I verified that each file is named correctly
  • I verified that each component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • I verified that the only data being stored in component state is data necessary for rendering and nothing else
  • In component 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)
  • I verified that component 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)
  • I verified that all JSX used for rendering exists in the render method
  • I verified that each 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

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

@Valforte Valforte requested review from a team as code owners April 23, 2026 15:50
@Valforte Valforte self-assigned this Apr 23, 2026
@melvin-bot melvin-bot Bot requested review from flaviadefaria and stitesExpensify and removed request for a team April 23, 2026 15:50
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 23, 2026

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

const [accountManagerReportID] = useOnyx(ONYXKEYS.ACCOUNT_MANAGER_REPORT_ID);
const [accountManagerReport] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${getNonEmptyStringOnyxID(accountManagerReportID)}`);
const accountManagerAccountID = getParticipantsAccountIDsForDisplay(accountManagerReport, false, true)?.at(0) ?? CONST.DEFAULT_MISSING_ID;
const [account] = useOnyx(ONYXKEYS.ACCOUNT);
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.

❌ PERF-11 (docs)

Subscribing to the full ONYXKEYS.ACCOUNT object when only accountManagerReportID and accountManagerAccountID are needed causes unnecessary re-renders whenever any unrelated field on the account changes. This is also inconsistent with AccountManagerLinkRenderer.tsx in this same PR, which correctly uses a selector for the same data.

Use a selector to extract only the needed fields:

const [accountManagerData] = useOnyx(ONYXKEYS.ACCOUNT, {
    selector: (account) => ({
        accountManagerReportID: account?.accountManagerReportID,
        accountManagerAccountID: account?.accountManagerAccountID,
    }),
});
const accountManagerReportID = accountManagerData?.accountManagerReportID;
const accountManagerAccountID = Number(accountManagerData?.accountManagerAccountID ?? CONST.DEFAULT_MISSING_ID);

Reviewed at: f68db34 | Please rate this suggestion with 👍 or 👎 to help us improve! Reactions are used to monitor reviewer efficiency.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...vider/HTMLRenderers/AccountManagerLinkRenderer.tsx 70.00% <100.00%> (+3.33%) ⬆️
src/pages/inbox/AccountManagerBanner.tsx 100.00% <100.00%> (+42.85%) ⬆️
...ges/workspace/workflows/WorkspaceWorkflowsPage.tsx 0.00% <0.00%> (ø)
... and 18 files with indirect coverage changes

@Valforte
Copy link
Copy Markdown
Contributor Author

@MelvinBot please review
@claude please review

@MelvinBot
Copy link
Copy Markdown
Contributor

Code Review — PR #88611

The approach is sound: reading accountManagerReportID and accountManagerAccountID from ONYXKEYS.ACCOUNT (populated by OpenApp/ReconnectApp) eliminates the race condition where the account-manager report hasn't loaded into Onyx yet.

Issues

  1. AccountManagerBannerNumber() coercion on a string ID
    accountManagerAccountID is typed as string | undefined on the Account type. The PR does:

    const accountManagerAccountID = Number(accountManagerData?.accountManagerAccountID ?? CONST.DEFAULT_MISSING_ID);

    This works, but other consumers of account.accountManagerAccountID (e.g. HelpPage, AssigneeStep, PolicyAccountingPage) pass the raw string directly to personal-details lookups or utility functions without Number() coercion. This inconsistency is minor but worth noting — if personalDetailsSelector expects a number, the coercion is correct; just make sure the personalDetailsSelector function signature actually takes a number.

  2. AccountManagerBanner — unused import
    The diff removes the usage of getParticipantsAccountIDsForDisplay but the original file still imports it:

    import {getParticipantsAccountIDsForDisplay, isConciergeChatReport} from '@libs/ReportUtils';

    The PR diff shows this was updated to only import isConciergeChatReport, which is correct. ✅ (Confirmed in the diff — this is fine.)

  3. WorkspaceWorkflowsPage — removed useOnyx but account was already loaded
    The PR correctly reuses the existing const [account] = useOnyx(ONYXKEYS.ACCOUNT) that was already present at line 125 and derives accountManagerReportID from it. This also removes one unnecessary Onyx subscription. ✅

  4. AccountManagerLinkRenderer — selector returns the full account object on every render
    The change:

    const [accountManagerReportID] = useOnyx(ONYXKEYS.ACCOUNT, {selector: (account) => account?.accountManagerReportID});

    This is good — the selector narrows the subscription so the component only re-renders when accountManagerReportID changes rather than on any account field change. ✅

Tests

  • New AccountManagerBannerTest covers the happy path, empty state, and regression guard against the legacy key. Good coverage.
  • Updated AccountManagerLinkRendererTest correctly uses the new Onyx shape.

Verdict

The change is correct and well-tested. One minor nit: confirm that the Number() coercion in AccountManagerBanner is intentional — if personalDetailsSelector accepts a number, it's fine; if it accepts string, the coercion is unnecessary.

Overall: Looks good

@Valforte
Copy link
Copy Markdown
Contributor Author

Valforte commented Apr 23, 2026

Confirmed intentional. src/selectors/PersonalDetails.ts:5 defines:

const personalDetailsSelector = (accountID: number) => ...

The selector takes a number, but account.accountManagerAccountID is typed as string | undefined. The Number() coercion is required — removing it reintroduces the typecheck error I fixed earlier (TS2345: Argument of type 'string | -1' is not assignable to parameter of type 'number').

Copy link
Copy Markdown
Contributor

@stitesExpensify stitesExpensify left a comment

Choose a reason for hiding this comment

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

Looks good!

@stitesExpensify
Copy link
Copy Markdown
Contributor

Let's get a c+ on this as well though!

@mkhutornyi
Copy link
Copy Markdown
Contributor

I'd like to review this as C+

@Valforte Valforte requested a review from mkhutornyi April 24, 2026 13:01
Copy link
Copy Markdown
Contributor

@flaviadefaria flaviadefaria left a comment

Choose a reason for hiding this comment

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

This fix makes sense to me from a product standpoint 👍

@mkhutornyi
Copy link
Copy Markdown
Contributor

mkhutornyi commented Apr 26, 2026

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.mov
Android: mWeb Chrome
iOS: HybridApp
ios.mov
iOS: mWeb Safari
msafari.mov
MacOS: Chrome / Safari
web.mov

Copy link
Copy Markdown
Contributor

@mkhutornyi mkhutornyi left a comment

Choose a reason for hiding this comment

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

QA Steps is missing. Otherwise looks good.

const {translate} = useLocalize();
const expensifyIcons = useMemoizedLazyExpensifyIcons(['Lightbulb']);
const [report] = useOnyx(`${ONYXKEYS.COLLECTION.REPORT}${getNonEmptyStringOnyxID(reportID)}`);
const [accountManagerReportID] = useOnyx(ONYXKEYS.ACCOUNT_MANAGER_REPORT_ID);
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.

NAB: ACCOUNT_MANAGER_REPORT_ID is not used anymore.
Should we completely remove this key from ONYXKEYS list?

@melvin-bot melvin-bot Bot requested a review from dangrous April 26, 2026 16:47
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 26, 2026

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

@melvin-bot melvin-bot Bot changed the title Fix empty Account Manager banner [Payment due @mkhutornyi] Fix empty Account Manager banner Apr 26, 2026
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Apr 26, 2026

🎯 @mkhutornyi, thanks for reviewing and testing this PR! 🎉

A payment issue will be created for your review once this PR is deployed to production.
E/E issue linked to the PR - no internal issue.

If payment is not needed (e.g., regression PR review fix etc), react with 👎 to this comment to prevent the payment issue from being created.

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

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

@Valforte Valforte merged commit 4f9b43d into main Apr 27, 2026
54 of 59 checks passed
@Valforte Valforte deleted the valforte/fixAccountManagerBanner branch April 27, 2026 13:38
@github-actions
Copy link
Copy Markdown
Contributor

🚧 @Valforte has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify
Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.62-13 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

No help site changes required.

This PR is a purely internal bug fix — it changes which Onyx key the Account Manager banner reads from (ONYXKEYS.ACCOUNT instead of ONYXKEYS.ACCOUNT_MANAGER_REPORT_ID) to fix a race condition. No user-facing behavior, feature names, or workflows changed.

I checked all 12 help site articles under App/docs/articles that mention "account manager" — they all refer to the human support role (e.g., "contact your account manager"), not the banner UI component this PR fixes.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.63-1 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

No help site changes required.

This PR is a bug fix for a race condition — it changes the internal data source for accountManagerAccountID but doesn't alter any user-facing behavior, feature names, workflows, or UI text. The Account Manager banner was always supposed to display; it just sometimes appeared empty due to a timing issue.

I reviewed all 61 help articles that reference "Account Manager" — they describe the Account Manager as a support contact role (e.g., "reach out to your Account Manager or Concierge"). None document the banner UI component or its rendering behavior, so no updates are needed.

@OSBotify
Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.64-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

No help site changes required.

This PR is an internal bug fix — it changes the Onyx data source for accountManagerAccountID and accountManagerReportID to avoid a race condition. There are no changes to user-facing behavior, UI text, feature names, or workflows.

I searched all articles under App/docs/articles that mention "Account Manager." They only reference it as a support role/contact (e.g., "Communicate with your Account Manager" or "Work with your account manager for this bespoke feed"). None describe the Account Manager banner UI component that this PR fixes, so no documentation updates are needed.

@IuliiaHerets
Copy link
Copy Markdown

Hi @Valforte. Can you please clarify how to create a workspace with an Account Manager?

cc @stitesExpensify @flaviadefaria @dangrous

@arosiclair arosiclair mentioned this pull request Apr 29, 2026
@johncschuster
Copy link
Copy Markdown
Contributor

I have QA'd this by support logging in to fitsetlt@valforte.dev's account. I have been set as the user's Account Manager.

Here's what that banner looks like:
2026-04-29_16-57-49

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.

8 participants