Skip to content

feat(brand): replace Gitgud logo - #99

Merged
cameroncuster merged 1 commit into
mainfrom
cameroncuster/replace-logo
Jul 24, 2026
Merged

feat(brand): replace Gitgud logo#99
cameroncuster merged 1 commit into
mainfrom
cameroncuster/replace-logo

Conversation

@cameroncuster

Copy link
Copy Markdown
Owner

Summary

  • replace the shared Gitgud logo and favicon with the new transparent 256×256 PNG
  • preserve the existing header dimensions, layout, routes, and visual design

Validation

  • pnpm run lint
  • pnpm run lint:es
  • pnpm run check
  • production build
  • desktop and mobile Playwright rendering checks

Scope

Only static/favicon.png changes.


Pull Request opened by Augment Code | View session

@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
gitgud Ready Ready Preview, Comment Jul 24, 2026 5:05pm

@cameroncuster
cameroncuster marked this pull request as ready for review July 24, 2026 17:05
@cameroncuster
cameroncuster merged commit 518aef9 into main Jul 24, 2026
6 checks passed
@cameroncuster
cameroncuster deleted the cameroncuster/replace-logo branch July 24, 2026 20:15
@cameroncuster

Copy link
Copy Markdown
Owner Author

🛰️ Verifier Report

🤖 Verifier · verifying cameroncuster/gitgud#99 @ 248735d

TL;DR: Built and served the PR-head app, then drove a real Chromium browser against it to confirm the new logo renders correctly in the site header on desktop and mobile with no console or network errors.

🔍 Walkthrough

  • Served the head build and confirmed the app serves the new asset at /favicon.png → the running server returned the exact head blob (fdf2d78, 69,343 B), not the parent's (247097b, 63,918 B).

    byte-exact match between the served file and the PR-head git blob
    served /favicon.png : HTTP 200, 69343 bytes, md5 432cb810…
    git head blob 248735d:static/favicon.png  →  fdf2d78, 69343 bytes, md5 432cb810…   ← identical
    git parent 60b0d85:static/favicon.png     →  247097b, 63918 bytes                  ← what mainline served
    

    Both parent and head are 256×256 8-bit RGBA (transparency preserved); only the artwork bytes differ.

  • The new logo renders in the header and the <img> fully loads on desktop — element decoded at its natural 256×256, laid out in the unchanged 48×48 slot:
    new logo rendered in desktop header next to gitgud.cc wordmark

  • Same logo renders correctly in the mobile header (393px viewport, hamburger nav intact):
    new logo rendered in mobile header

  • What actually changed — before → after artwork (same mascot, refreshed lines; header dimensions and layout unchanged):
    before vs after favicon artwork side by side

📋 Scope

Under test: PR #99 swaps static/favicon.png for a new transparent 256×256 PNG. The asset is consumed in exactly two places: the header logo (Header.svelte<img src="/favicon.png" class="h-12 w-12 object-contain">) and the browser-tab icon (app.html<link rel="icon" href="…/favicon.png">). Verified by building the head, serving it with vite preview, and rendering / in real Chromium (desktop + mobile).

Not tested:

  • The browser-tab favicon as painted by the browser chrome — the <link rel="icon" href="./favicon.png"> tag is present in the served HTML and resolves to the new asset (HTTP 200), but the OS/browser tab bitmap itself isn't screenshot-able headlessly. Covered by the same file the header loads.
  • Static gates (lint, lint:es, check, build) — CI's job, not re-run here. The build was run only to stand the app up, and it succeeded.
  • Supabase / data flows — untouched by this diff and irrelevant to a static asset swap (served the build against a stub Supabase URL).

📦 Artifacts · desktop header · mobile header · before/after · full page


Don't like what you see? Add a verification skill so the next run tests this kind of change.

Want another run? Comment cosmos verify on this change request.

👍 / 👎 · View session

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.

1 participant