Skip to content

[Tracking] Design polish items #100792

Open
11 of 12 issues completed
Open

Description

@shawnborton

This tracking issue covers the various design polish items we want to implement across both web and mobile. See Slack (internal) for more context on this project.

Sub-issues (I will be making these shortly):

  • Use .5px borders on table rows for mobile
  • Reduce size of credit card avatars
  • Add brand magic to Home > Concierge card

cc @dubielzyk-expensify @dannymcclain @grgia @JmillsExpensify

Issue OwnerCurrent Issue Owner: @huult

Activity

  1. grgia commented on Sep 10, 2026

    @grgia
    Contributor

    🤟 Rad

  2. 1 remaining item

  3. shawnborton commented on Sep 11, 2026

    @shawnborton
    ContributorAuthor

    Is it okay for you to be a co-author but also a PR approver?

  4. huult commented on Sep 11, 2026

    @huult
    Contributor

    Is it okay for you to be a co-author but also a PR approver?

    @shawnborton In the MelvinBot workflow, C+ should be added as a co-author so we can provide feedback and request updates directly after reviewing.

    For the current bugs, once we agree on and approve Melvin’s proposal, Melvin creates the PR and assigns the C+ as a co-author to review and provide feedback. If we’re only reviewers, MelvinBot won’t be able to implement our feedback directly. We would have to wait for you to assign the implementation to Melvin, which adds an extra step and takes more time. It would be more efficient if C+ could be a co-author and provide feedback directly to MelvinBot.

  5. shawnborton commented on Sep 11, 2026

    @shawnborton
    ContributorAuthor

    Okay cool, let's get a quick confirmation from @grgia - I thought we never wanted the reviewer to also be a PR author per our compliance policies.

  6. huult commented on Sep 11, 2026

    @huult
    Contributor

    @shawnborton For example, here are PRs #100360 and #100672 where I worked with MelvinBot. 😄

  7. shawnborton commented on Sep 11, 2026

    @shawnborton
    ContributorAuthor

    Totally, I get where you are coming from and I see where this makes life much easier for you as a reviewer! I just want to check internally to make sure this is expected and okay.

  8. huult commented on Sep 11, 2026

    @huult
    Contributor

    Yeah, totally agree. While we’re waiting for confirmation, I’ll continue reviewing and providing feedback.

  9. grgia commented on Sep 11, 2026

    @grgia
    Contributor

    @shawnborton @huult it's technically fine so long as there is one employee non-author review

  10. shawnborton commented on Sep 11, 2026

    @shawnborton
    ContributorAuthor

    Great! @huult going to assign you to the PRs then

  11. huult commented on Sep 14, 2026

    @huult
    Contributor

    @shawnborton @grgia I’ve finished reviewing these 4 PRs and left feedback for MelvinBot to update. They’ve been approved and are ready for your final review and merge:

    #100817
    #100832
    #100805
    #100835
    #100881
    #100831

    I also looked through these 2 PRs, but they don’t seem ready yet. I’ve asked @grgia and @shawnborton to take a look. Please tag me when they’re ready for another review:

    #100881 -> @grgia #100881 (comment)
    #100831 -> @shawnborton #100831 (comment)

  12. shawnborton commented on Sep 14, 2026

    @shawnborton
    ContributorAuthor

    Sounds good, responded to or merged the PRs above.

  13. added
    Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.
    on Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

MonthlyKSv2Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions