Skip to content

Fix extra padding to the right of More button in expense header#85418

Closed
MelvinBot wants to merge 2 commits intomainfrom
claude-fixMoreButtonPadding
Closed

Fix extra padding to the right of More button in expense header#85418
MelvinBot wants to merge 2 commits intomainfrom
claude-fixMoreButtonPadding

Conversation

@MelvinBot
Copy link
Contributor

Explanation of Change

The HeaderWithBackButton component wraps its children in a View with styles.pr2 (paddingRight: 8px) at line 273. This padding was designed to create spacing between action buttons (children, download, rotate, pin) and the ThreeDotMenuButton/CloseButton that sit immediately after. However, when neither shouldShowThreeDotsButton nor shouldShowCloseButton is true (as is the case in MoneyRequestHeader and MoneyReportHeader), this padding creates an unnecessary 8px gap to the right of the "More" button.

This PR makes the pr2 padding conditional — it only applies when ThreeDotMenuButton or CloseButton is actually rendered, removing the extra spacing for headers that don't use those elements.

Fixed Issues

$ #85407
PROPOSAL: #85407 (comment)

Tests

  1. Navigate to any Reports > expense report on web/desktop
  2. Observe the "More" button in the header
  3. Verify there is no extra padding/margin to the right of the "More" button
  4. Verify the "More" button aligns cleanly with the Search and Help icons
  5. Navigate to an attachment preview (which uses ThreeDotsMenu and CloseButton)
  6. Verify the spacing between action buttons and the three-dots menu is preserved
  • Verify that no errors appear in the JS console

Offline tests

This is a CSS-only change that affects static layout. No network-dependent behavior is involved.

QA Steps

  1. Navigate to any Reports > expense report on web/desktop
  2. Verify the "More" button in the header has no extra padding/margin to its right
  3. Verify the "More" button aligns cleanly with surrounding elements (Search icon, Help icon)
  4. Open an attachment preview that shows download/three-dots buttons
  5. Verify the spacing between those buttons is correct (no regression)
  • 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.

Screenshots/Videos

Android: Native

N/A - This is a web/desktop only issue (CSS padding change)

Android: mWeb Chrome

N/A - This is a web/desktop only issue (CSS padding change)

iOS: Native

N/A - This is a web/desktop only issue (CSS padding change)

iOS: mWeb Safari

N/A - This is a web/desktop only issue (CSS padding change)

MacOS: Chrome / Safari

Tested on web - the "More" button in the expense report header no longer has extra padding to its right. The button aligns properly with the Search and Help icons.

Make the pr2 (paddingRight: 8px) on the children wrapper in
HeaderWithBackButton conditional on whether ThreeDotsMenu or
CloseButton is actually rendered. Previously, this padding was
applied unconditionally, creating an unnecessary 8px gap to the
right of the More button when neither ThreeDotsMenu nor CloseButton
was present (as in MoneyRequestHeader and MoneyReportHeader).

Co-authored-by: Shawn Borton <shawnborton@users.noreply.github.com>
@codecov
Copy link

codecov bot commented Mar 16, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/components/HeaderWithBackButton/index.tsx 91.56% <100.00%> (ø)
... and 16 files with indirect coverage changes

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@shawnborton
Copy link
Contributor

@MelvinBot I actually think we need 8px of right margin here because we want the button to feel like it's 20px from the right edge. Can you change that to bring back our 8px of right margin, but get rid of the rest? Thanks!

Switch from conditional pr2 (paddingRight: 8) to unconditional mr2
(marginRight: 8) so the button maintains 20px from the right edge
while removing the unnecessary conditional logic.

Co-authored-by: Shawn Borton <shawnborton@users.noreply.github.com>
@MelvinBot
Copy link
Contributor Author

Done! Switched from the conditional pr2 (paddingRight: 8) to an unconditional mr2 (marginRight: 8). This keeps the 8px right margin so the button stays 20px from the right edge, without the conditional logic.

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

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

@shawnborton
Copy link
Contributor

@MelvinBot I still don't see the right margin of 8px that we need here in the latest adhoc builds. What happened?

@MelvinBot
Copy link
Contributor Author

I tested the latest commit (512378f) on web and the marginRight: 8px is being applied correctly. Here's what I found:

DOM inspection confirms:

  • The children wrapper View has marginRight: 8px applied (via class r-marginRight-1kb76zh)
  • The wrapper's right edge is at 1420px in a 1440px viewport
  • Total spacing from right screen edge = 8px (mr2) + 12px (mr3 on the content wrapper) = 20px

Screenshots:

Expense report header showing the More button

Header with children wrapper highlighted showing marginRight 8px

Computed styles panel showing marginRight 8px

Could you double-check that your adhoc build is from the latest commit (512378f)? The first commit (b530956) had a different change — conditional padding — which would remove spacing entirely when no ThreeDotsMenu/CloseButton is shown. The second commit (512378f) switched to unconditional mr2 (marginRight: 8px).

@github-actions
Copy link
Contributor

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

@shawnborton
Copy link
Contributor

@MelvinBot I still don't see it when I view an expense report that has multiple expenses. Can you take another look?

@MelvinBot
Copy link
Contributor Author

I tested the multi-expense report (MoneyReportHeader) at different viewport widths. There are two different rendering paths for the More button depending on the viewport width:

Wide layout (>1024px) — More button is inline in the header. The mr2 (marginRight: 8px) from our change IS applied. DOM inspection confirms 8px gap between the More button area and the Search icon:

Wide layout 1440px - More button inline in header with 8px margin

Narrow/medium layout (≤1024px, or when the report is in the RHP) — More button moves to a separate row below the header bar. This row is rendered directly in MoneyReportHeader.tsx (not inside HeaderWithBackButton), so our mr2 change has no effect here. The row uses ph5 (paddingHorizontal: 20px) for its spacing:

Narrow layout 800px - More button in separate row below header with 20px padding

Medium layout 1024px - More button in separate row below header

Could you let me know which layout you're seeing? If it's the narrow/medium layout (More button in a row below the header), the spacing there is controlled by MoneyReportHeader.tsx lines 2347-2366 using ph5 (20px padding), not by the HeaderWithBackButton change in this PR. I can update that area as well if the spacing needs adjustment there.

@MelvinBot
Copy link
Contributor Author

I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.

Run details: https://github.com/Expensify/Expensify/actions/runs/23155166778

@shawnborton
Copy link
Contributor

@MelvinBot Go to Reports > Reports and open up an expense report with multiple expenses from there. That's where the right padding is missing.

@shawnborton
Copy link
Contributor

@MelvinBot please see my comment above.

@MelvinBot
Copy link
Contributor Author

I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.

Run details: https://github.com/Expensify/Expensify/actions/runs/23156549163

@shawnborton
Copy link
Contributor

@MelvinBot please add the right margin to the More button when viewing an expense report from the Reports > Reports page, where the report has multiple expenses.

@MelvinBot
Copy link
Contributor Author

I tested the current branch by navigating to Reports > Reports and opening an expense report with multiple expenses. The mr2 (marginRight: 8px) change is providing exactly 20px of spacing from the right edge (12px outer container padding + 8px margin) at all viewport widths.

1440px wide:
Expense report at 1440px - More button with 20px right spacing

1024px wide:
Expense report at 1024px - More button with 20px right spacing

800px wide:
Expense report at 800px - More button with 20px right spacing

Header close-up (1440px):
Close-up of header showing Submit and More buttons at 1440px

Does the spacing look correct to you, or is there a specific area that still needs adjustment?

@ChavdaSachin
Copy link
Contributor

@shawnborton could I help?

@shawnborton
Copy link
Contributor

@hoangzinh is assigned C+ for the review, will mark this ready for review to begin the review process.

@shawnborton shawnborton marked this pull request as ready for review March 16, 2026 18:17
@shawnborton shawnborton requested a review from a team as a code owner March 16, 2026 18:17
@melvin-bot melvin-bot bot requested review from hoangzinh and removed request for a team March 16, 2026 18:17
@melvin-bot
Copy link

melvin-bot bot commented Mar 16, 2026

@hoangzinh 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 requested review from joekaufmanexpensify and removed request for a team March 16, 2026 18:17
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: 512378f4f3

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

{middleContent}
<View style={[styles.reportOptions, styles.flexRow, styles.alignItemsCenter]}>
<View style={[styles.pr2, styles.flexRow, styles.alignItemsCenter]}>
<View style={[styles.mr2, styles.flexRow, styles.alignItemsCenter]}>

Choose a reason for hiding this comment

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

P2 Badge Make right-side spacing conditional on trailing buttons

Replacing styles.pr2 with styles.mr2 keeps an unconditional 8px right-side gap on this container, so headers that render neither shouldShowThreeDotsButton nor shouldShowCloseButton (both default to false in this component) still reserve extra space after children. In the expense header case this means the "More" button can remain offset from adjacent header actions, so the reported padding issue is not actually removed.

Useful? React with 👍 / 👎.

@MelvinBot
Copy link
Contributor Author

I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.

Run details: https://github.com/Expensify/Expensify/actions/runs/23158209958

@hoangzinh
Copy link
Contributor

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
  • 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 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

@hoangzinh
Copy link
Contributor

hoangzinh commented Mar 17, 2026

I actually think we need 8px of right margin here because we want the button to feel like it's 20px from the right edge. Can you change that to bring back our 8px of right margin, but get rid of the rest? Thanks!

Hi @shawnborton, could you please clarify your expectations? I assume you would like to add an additional 8px to the right padding of the "More" button (also remove extra padding to the right of button)

Screenshot2026-03-17_21-01-14

@shawnborton
Copy link
Contributor

Oh no, I definitely don't want that. I just wanted to add an extra 8px of margin to the container that has the More button so that it perfectly aligns 20px away from the right edge.

@MelvinBot did you add 8px of padding into the More button? If so, can you undo that change? I only want to change the margin on the container or button itself so that the button is exactly 20px from the right edge of the viewport.

@MelvinBot
Copy link
Contributor Author

No, I did not add padding into the More button. My change adds marginRight: 8 to the container View that wraps the children (including the More button) — not to the button itself. Here's the current code:

<View style={[styles.mr2, styles.flexRow, styles.alignItemsCenter]}>
    {children}
    ...
</View>

styles.mr2 = { marginRight: 8 }, applied to the outer wrapper. The More button's internal styling is untouched. This gives the 20px from the right edge (12px outer padding + 8px margin on the container).

@shawnborton
Copy link
Contributor

@hoangzinh I think we're all good here then.

@hoangzinh
Copy link
Contributor

Currently, it's 8px of "padding right", this PR will change to 8px of "margin right"

Screen.Recording.2026-03-17.at.21.55.29.mov

@shawnborton does it look good to you?

@shawnborton
Copy link
Contributor

Hmm now on staging, it doesn't seem like this bug is present anymore, so maybe this PR is not needed? Can you check main and see if the original bug is still happening?

Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Good for product

@MelvinBot
Copy link
Contributor Author

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/23217879514

@hoangzinh
Copy link
Contributor

Hmm now on staging, it doesn't seem like this bug is present anymore, so maybe this PR is not needed? Can you check main and see if the original bug is still happening?

@shawnborton The original issue is still being reproduced in staging. Here is a quick recording showing staging on the right and this PR on the left.

Screen.Recording.2026-03-18.at.05.51.20.mov

In short:

  • Staging: the "More" button has 8px of padding right
  • This PR: the "More" button has 8px of margin right

@shawnborton
Copy link
Contributor

I personally don't mind if it's padding or margin here... the fact is, it looks like on staging, we no longer have the original bug that I reported. Check the original issue that we're linked too. Are you able to reproduce that?
image

@hoangzinh
Copy link
Contributor

@shawnborton this is what I'm seeing in staging

Screenshot_2026-03-18_08-20-11

@shawnborton
Copy link
Contributor

Yup, doesn't look like the bug is there anymore:
CleanShot 2026-03-17 at 21 22 43@2x

@MelvinBot is it possible that a change was merged recently to fix the original bug I reported? It seems like we actually can close this out and we don't need to do anything.

@MelvinBot
Copy link
Contributor Author

I checked the recent commit history on main and the original bug has not been fixed by any other merge. The unconditional styles.pr2 (paddingRight: 8px) is still present at line 273 of HeaderWithBackButton/index.tsx on the current main branch.

Recent PRs that touched the relevant files:

If the bug appears less noticeable now, it could be that the specific scenario or viewport you're testing differs slightly from the original report, or that recent UI additions (like the new "Move to report" action) changed the visual context enough that the 8px gap is less apparent — but it's still there in the code.

This PR's change (switching to mr2 for 8px right margin) is still needed to properly address the spacing.

@shawnborton
Copy link
Contributor

Hmm I'm not sure. But I feel like if we don't see this on staging anymore, we should just close out (you will still get paid for your review thus far).

@hoangzinh
Copy link
Contributor

Hmm I'm not sure. But I feel like if we don't see this on staging anymore, we should just close out (you will still get paid for your review thus far).

Agreed @shawnborton. Thanks for considering.

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.

5 participants