Skip to content

CS color change#26

Open
sahusw wants to merge 3 commits into
devfrom
cs-color
Open

CS color change#26
sahusw wants to merge 3 commits into
devfrom
cs-color

Conversation

@sahusw
Copy link
Copy Markdown

@sahusw sahusw commented Apr 9, 2026

Changed both the CS route color and the color of its png to be a lighter shade of blue because some users were complaining that it blended in in dark mode.

Refactor

One semi-related issue: Could also change the color of some of The Ride routes with a similar shade of blue (would require changing their corresponding PNGs, which is more work)

Changes made: Backend (Typescript)

Tested on: iOS Simulator (in both dark mode and light mode)

Original:
Screenshot 2026-04-08 at 11 38 22 PM
Modified:
Screenshot 2026-04-09 at 8 58 37 AM
Screenshot 2026-04-09 at 8 59 24 AM

*Note: forgot to follow the commit format for first 2 commits. For commit 9e8b55b, fix(backend): Changed CS color in backend\n Changed CS color in backend from #3559B8 (dark blue) to #0099FF (lighter blue) because some users were complaining that CS looked too dark in dark mode. For commit a5716c5, fix(backend): Modified the bus_CS.png using Photoshop\n Modified the bus_CS.png so that the CS bus color would match the new CS route color.

sahusw added 3 commits April 8, 2026 13:20
reset the ride colors i modified to their orig color (#086CB6) bc i realized i would have to modify their bus png color to match the route color, and i didn't do that
Copy link
Copy Markdown
Member

@jumpy-cat jumpy-cat left a comment

Choose a reason for hiding this comment

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

Tested on android simulator and the changes look good! For commit messages in the future, you can do an interactive rebase before pushing your changes to change messages, merge/split commits, and clean things up.

In this case you've already pushed the changes, which makes things a bit more complicated. If you want to fix the history do one of the following:

  1. use an interactive rebase to fix the messages, then do a force push git push --force-with-lease (generally never force push unless everyone who has the branch locally is aware, should be fine in this case)
  2. (safer but slightly more work) create a new branch, cherry pick the commits over, interactive rebase, push

Let me know if you want to try one of these, or if you want me to handle it.

Regarding the ride, it seems like the routes are a better shade of blue compared to what CS was, so its probably ok.

Image

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.

2 participants