feat: rebrand portal from <GET A JOB> to <hype> - #32
Merged
Conversation
Contributor
Author
|
Reviewed: pure brand-string rename across static + generated + backend surfaces, no logic change. Leak grep clean (no homelab specifics in diff or messages). CI green — hub and TBC Note for deploy: the static surfaces update on the next deploy pull; the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Renames the guild portal brand from
<GET A JOB>to<hype>across every surface:--checkpasses)URLs, repo path, service names, and asset filenames are unchanged.
Why
The name change is the first phase of the rebrand. Art and asset renames follow separately so this PR has no deploy dependency beyond a normal deploy pull for the static surfaces.