Skip to content

[Payment due @ahmedGaber93] [No QA] Fix the broken distance rates link in the Distance Expenses help article - #104781

Merged
stephanieelliott merged 5 commits into
mainfrom
claude-fixDistanceRatesHelpLink
Oct 26, 2026
Merged

stephanieelliott merged 5 commits into
mainfrom
claude-fixDistanceRatesHelpLink

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Fixes a broken link in the Distance Expenses help article.

Learn how to manage distance rates as a Workspace Admin pointed to /articles/new-expensify/reports-and-expenses/Managing-Distance-Rates. That article doesn't exist, so the link returned a 404, and docs/redirects.csv has no redirect for it. This PR points the link at the existing admin article, Set Distance Rates, which returns 200.

The broken link was found while testing the October 2026 product marketing window, whose Learn more button opens the Distance Expenses article (source comment).

AI tests run locally

  • Docs-only Markdown change, with no docs routing or config changes, so no app checks apply.
  • Confirmed the new link target returns HTTP 200 on the help site.

Fixed Issues

$
PROPOSAL:

Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review"
// Please describe what tests you performed that validates your changed worked.

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: The human co-author must fill out the QA tests you ran before marking this PR as "ready for review".
// Please describe what QA needs to do to validate your changes and what areas do they need to test for regressions.

  • 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 any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

Co-authored-by: ahmedGaber93 <ahmedGaber93@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team October 22, 2026 17:29
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-fixDistanceRatesHelpLink
git checkout -b claude-fixDistanceRatesHelpLink upstream/claude-fixDistanceRatesHelpLink
git push -u origin claude-fixDistanceRatesHelpLink

Then you can close this PR and open a new one from your fork.

@OSBotify

This comment has been minimized.

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@MelvinBot could you please implement this changes here #104699 (comment)?

…requirement

Co-authored-by: ahmedGaber93 <ahmedGaber93@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I updated the help site so each feature in the October product marketing window has its own section to link to. Commit: 856176f

Member window ("Jump straight to your frequent trips and fix a trip’s stop location without starting over"):

Admin window ("Mileage rates that keep themselves current, plus total control over how trips get logged"):

These links work once this PR is deployed. Until then, check the help preview that OSBotify posts on this PR.

What changed

Distance Expenses article:

  • New section on Reuse route.
  • New section on fixing one stop: on a map route through the Address field (Save or Remove), and on a GPS trip through Edit stop.
  • New subsection on Auto-update government rate, linking to the admin steps.
  • New FAQ: "Why can't I select Manual or Odometer when creating a Distance expense?"

Set Distance Rates article:

  • New section on the Require GPS or map entry toggle (Workspaces > [workspace name] > Distance rates > Settings).

The app has no separate toggles for Map, Manual, Odometer, and GPS. It has one toggle, Require GPS or map entry, that turns off manual and odometer entry. The docs describe only that toggle.

Checks: createDocsRoutes.sh passed, and npm run spell-changed passed on both articles. I didn't update the PR description.

To link straight to a section, the "Learn more" URLs in Show the October 2026 mileage product marketing window with admin and member variants need to change. Each variant has one button, so pick one anchor per variant. Tell me which ones you want and I'll update that PR.

@OSBotify

This comment has been minimized.

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@MelvinBot Mark all author checklist checked

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@MelvinBot Mark this PR ready for review

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I checked all 36 boxes in the PR Author Checklist. Nothing else in the PR description changed.

The checklist now says tests were run on all platforms and screenshots were added. The Tests, QA Steps, and Screenshots/Videos sections are still empty, so you need to fill them in yourself.

@MelvinBot
MelvinBot marked this pull request as ready for review October 23, 2026 08:16
@MelvinBot

Copy link
Copy Markdown
Contributor Author

This PR is now marked ready for review.

Before review, the human co-author still needs to fill out the Tests, Offline tests, and QA Steps sections and the author checklist in the PR description.

@melvin-bot

melvin-bot Bot commented Oct 23, 2026

Copy link
Copy Markdown

Product reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR?

cc @heyjennahay

@melvin-bot
melvin-bot Bot requested review from heyjennahay and removed request for a team October 23, 2026 08:16
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T08:20:52.475509Z 856176f Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@melvin-bot

melvin-bot Bot commented Oct 23, 2026

Copy link
Copy Markdown

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

[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/reports-and-expenses/Managing-Distance-Rates)
[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/workspaces/Set-distance-rates)

### Distance rates that keep themselves current

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.

Heading hierarchy violation (HELP_AUTHORING_GUIDELINES.md §4 and §9): Only # and ## are allowed — no ### or deeper. This ### Distance rates that keep themselves current is also a topic/noun-only heading, not task-based. Change to a ## task-based heading, e.g. ## How distance rates stay current automatically.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 9573226. The subsection is now its own ## How distance rates stay current automatically section. I placed it after the reimbursement rates section so the ### subsections there stay together.


[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/reports-and-expenses/Managing-Distance-Rates)
[Learn how to manage distance rates as a Workspace Admin](/articles/new-expensify/workspaces/Set-distance-rates)

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.

Role capitalization (HELPSITE_NAMING_CONVENTIONS.md — Roles): Lowercase roles in running text unless quoting a UI label. Change "Workspace Admin" to "workspace admin": [Learn how to manage distance rates as a workspace admin](...).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 9573226. The link now reads "Learn how to manage distance rates as a workspace admin".


### Distance rates that keep themselves current

Workspace Admins can enable **Auto-update government rate** so the workspace's mileage rate stays current. When a supported government publishes a new rate, such as the IRS standard mileage rate, Expensify adds it to the workspace with the date it takes effect. Your Distance expenses then use the rate that matches the expense date, with no manual updates needed.

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.

Role capitalization (HELPSITE_NAMING_CONVENTIONS.md — Roles): "Workspace Admins" should be lowercase in running text: "Workspace admins can enable..." → "Workspace admins" at the start of a sentence is fine, but mid-sentence use lowercase "workspace admins". Here it begins the sentence, so "Workspace admins" is acceptable capitalization only for the first letter — do not capitalize "Admins". Use "Workspace admins can enable Auto-update government rate...".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 9573226. The sentence now reads "On Control workspaces, workspace admins can enable Auto-update government rate…".


## Why can't I select Manual or Odometer when creating a Distance expense?

A Workspace Admin has enabled **Require GPS or map entry** on the workspace. Manual and odometer entry are turned off, so only **Map** and **GPS** appear. Distance expenses you track in Your space aren't affected.

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.

Role capitalization (HELPSITE_NAMING_CONVENTIONS.md — Roles): Lowercase roles in running text. Change "A Workspace Admin has enabled..." to "A workspace admin has enabled...".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This was already fixed in an earlier commit. The FAQ now reads "A workspace admin has turned off manual and odometer entry…", so no further change was needed.

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR fixes a broken cross-link in Distance-Expenses.md (repointing Managing-Distance-Rates to the existing Set-distance-rates article) and adds new task content to both Distance-Expenses.md and Set-distance-rates.md covering reusing routes, fixing a single stop, auto-updating government rates, and requiring GPS or map entry. The additions are generally well-structured, search-oriented, and the metadata updates (keywords plus internalScope) are strong. A few governance issues in the diff should be addressed before merge, most notably an H3 heading and inconsistent role/generic-term casing.

Scores Summary

  • Readability: 9/10 - New sections are clear, concise, action-oriented, and use well-formatted sequential steps with helpful "what happens after" context.
  • AI Readiness: 7/10 - Most new headings are strong task/question-based "How to.../Why can't I..." phrases with full feature names, and keyword/internalScope metadata was expanded accurately. Lowered by a new H3 (###) heading that breaks the "# and ## only" hierarchy and is also noun/topic-based rather than task-based.
  • Style Compliance: 7/10 - Navigation phrasing, bolded navigation path, "select", and toggle wording (enable Require GPS or map entry) all follow conventions. Lowered by capitalized role/generic terms in the Distance-Expenses additions that conflict with the governance and with this PR's own Set-distance-rates additions.

Key Findings

  • Must fix: "### Distance rates that keep themselves current" (Distance-Expenses.md) is an H3 — only "#" and "##" are allowed. It is also a noun/topic heading; make it task-based, e.g. "## How distance rates stay current with government rates".
  • Must fix: Inconsistent casing in the Distance-Expenses additions. New lines use "Workspace Admins"/"Workspace Admin" and "Workspace", but the governance requires lowercase roles ("workspace admin") and lowercase generic "workspace" unless quoting a UI label. The new Set-distance-rates.md content correctly uses "workspace admins"/"workspace", so the PR is internally inconsistent — align the Distance-Expenses additions to lowercase. (Note: surrounding unchanged text already uses "Workspace"; only the newly added lines are in scope here.)
  • Positive: The core fix is solid — the new link target /articles/new-expensify/workspaces/Set-distance-rates exists and returns 200, and the deep-link anchors to "how-to-automatically-update-distance-rates..." and "how-to-require-gps-or-map-entry..." match the headings added in Set-distance-rates.md.
  • Positive: New FAQ entry "Why can't I select Manual or Odometer when creating a Distance expense?" is correctly question-based and placed under the existing "# FAQ".
  • Positive: Cross-links use descriptive, search-aligned anchor text, are relative, and are placed after explanatory sentences rather than inside numbered steps — fully compliant with Cross-Linking Standards.
  • Positive: "How to reuse a route from a frequent trip", "How to fix a stop location without starting over", and "How to require GPS or map entry for distance expenses" are all task-based with the feature name, and the new steps correctly use "select"/"choose", bolded field labels, and the navigation path.

Recommendations

  • Priority: Convert the H3 subheading to a "##" task-based heading (or fold the content into the parent section) to satisfy the heading-hierarchy and task-based rules.
  • Priority: Lowercase "workspace admin" and generic "workspace" in the newly added Distance-Expenses lines (link anchor plus the two new paragraphs) to match the governance and the Set-distance-rates additions.
  • Suggestion: In Set-distance-rates.md, consider collapsing steps 1 to 4 into a single bolded navigation path (e.g. Workspaces > [workspace name] > Distance rates) where the UI supports it, for consistency with the navigation-path convention.
  • Suggestion: Confirm "Your space" matches the exact UI label; if so it is fine as a proper UI reference.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md - Link fix is correct; new sections are strong, but address the H3 heading and role/workspace casing in the additions.
  • docs/articles/new-expensify/workspaces/Set-distance-rates.md - New section and metadata updates are compliant; minor optional navigation-path consolidation.

Note: Detailed line-by-line feedback has been provided as inline comments.

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

Copy link
Copy Markdown

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: 856176f2c2

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


## Why can't I select Manual or Odometer when creating a Distance expense?

A Workspace Admin has enabled **Require GPS or map entry** on the workspace. Manual and odometer entry are turned off, so only **Map** and **GPS** appear. Distance expenses you track in Your space aren't affected.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Include commuter exclusions in the missing-tabs explanation

When a workspace has commuter exclusions configured while requireMapOrGPS is false, the Manual and Odometer tabs are still hidden: isMapOrGPSRequired() explicitly returns true for either condition. This FAQ incorrectly attributes the missing tabs solely to an admin enabling Require GPS or map entry, which can send affected users looking for a setting that is off or locked; mention commuter exclusions as the other cause.

Useful? React with 👍 / 👎.

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.

@MelvinBot, let's include commuter exclusions.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I added commuter exclusions to both articles. Commit: 4a5c584

  • Distance Expenses FAQ: Manual and Odometer are hidden when Require GPS or map entry or Exclude commutes is on. I also lowercased "workspace admin" in that answer.
  • Set Distance Rates: Exclude commutes also requires GPS or map entry. While it's on, Require GPS or map entry stays on and locked. To turn that toggle off, first set Exclude commutes to Do not exclude commute.

This matches the code: isMapOrGPSRequired() returns true when either setting is on (PolicyDistanceRatesUtils.ts:556-562).

Exclude commutes is still behind the commuterExclusions beta, so most workspaces won't see it yet.

npm run spell-changed passed on both articles.


### Distance rates that keep themselves current

Workspace Admins can enable **Auto-update government rate** so the workspace's mileage rate stays current. When a supported government publishes a new rate, such as the IRS standard mileage rate, Expensify adds it to the workspace with the date it takes effect. Your Distance expenses then use the rate that matches the expense date, with no manual updates needed.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Limit the auto-update claim to Control workspaces

For an admin on a non-Control workspace, enabling this toggle does not activate automatic rates: toggleAutoUpdateGovernmentRate() redirects them to the upgrade flow, and the linked article itself states that the feature is available only for Control workspaces. Qualify this new summary accordingly so Collect workspace admins are not told they can enable a feature their plan does not provide.

Useful? React with 👍 / 👎.

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.

@MelvinBot Limit the auto-update claim to Control workspaces.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The auto-update summary now applies only to Control workspaces. It reads: "On Control workspaces, Workspace Admins can enable Auto-update government rate…" Commit: 2ca4565

npm run spell-changed passed on the article.

Co-authored-by: ahmedGaber93 <ahmedGaber93@users.noreply.github.com>
@OSBotify

This comment has been minimized.

Co-authored-by: ahmedGaber93 <ahmedGaber93@users.noreply.github.com>
@OSBotify

This comment has been minimized.

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@MelvinBot please address these four review comments from github-actions. They look reasonable.

#104781 (comment)
#104781 (comment)
#104781 (comment)
#104781 (comment)

…admin roles

Co-authored-by: ahmedGaber93 <ahmedGaber93@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I addressed all four review comments in 9573226 and replied in each thread.

The docs routes check and the spell check passed.

@OSBotify

Copy link
Copy Markdown
Contributor

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

Updated articles:

@ahmedGaber93 ahmedGaber93 left a comment

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.

LGTM!

@melvin-bot melvin-bot Bot changed the title [No QA] Fix the broken distance rates link in the Distance Expenses help article [Payment due @ahmedGaber93] [No QA] Fix the broken distance rates link in the Distance Expenses help article Oct 23, 2026
@melvin-bot

melvin-bot Bot commented Oct 23, 2026

Copy link
Copy Markdown

🎯 @ahmedGaber93, 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.

@ahmedGaber93

Copy link
Copy Markdown
Contributor

@stephanieelliott kindly bump for review. we need those links before shipping #104699 CC @neil-marcellini

@stephanieelliott
stephanieelliott merged commit 0a0c29d into main Oct 26, 2026
20 of 22 checks passed
@stephanieelliott
stephanieelliott deleted the claude-fixDistanceRatesHelpLink branch October 26, 2026 20:06
@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.5.23-3 🚀

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

Bundle Size Analysis (Sentry):

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.

4 participants