[codex] Fix mobile chat input and profile links#121
Merged
Conversation
83b8e08 to
85ae952
Compare
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.
Summary
web/distfor future pull requests.Why
On mobile Safari-style layouts, the chat input could appear poorly because it was a transparent borderless input inside a compact flex row. The hero also still described the page as an agent, while this view should present plain social links such as LinkedIn and GitHub.
The repo only had a production GitHub Pages deployment for
main; the new PR Preview workflow creates a lightweight staging artifact without adding hosting infrastructure or touching production deploys.Validation
npm testnpm run buildVITE_BASE_PATH=./ npm run buildnpx playwright test e2e/portfolio-layout.spec.ts.github/workflows/pr-preview.ymlwith PyYAML.Note
GitHub only exposes/runs a newly added workflow after the workflow file exists on the default branch, so the PR Preview workflow will start producing artifacts for subsequent PRs after this lands.