fix: make Get help from an expert cards actionable - #175
Open
NckNA wants to merge 1 commit into
Open
Conversation
Signed-off-by: NckNA <ded8z8ded@gmail.com>
|
@NckNA is attempting to deploy a commit to the gibwork Team on Vercel. A member of the Team first needs to authorize it. |
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
siteConfig.appUrlso the landing page does not hardcode undocumented internal create routesaria-labelsCloses #31.
Why
The current cards look interactive but are plain
Cardcomponents with no link or click handler. On both desktop and mobile a user can click them and nothing happens. This patch gives the whole card a semantic anchor and sends users to the current Gibwork app, where the existing Create flow lives.Validation
git diff --checkpassescomponents/looking-for.tsxnpm ci --ignore-scriptscould not run because the repository currentpackage.jsonandpackage-lock.jsonare already out of sync (for example missing locked PostHog/Sharp dependencies); I did not modify the upstream lockfile as part of this focused fixAI disclosure
This contribution was prepared with AI assistance. The repository and task inputs were treated as untrusted data, the patch was scoped manually to the reported issue, and no external runtime or repository-provided install script was executed.