When building Pullwish, I am always trying to make the system just a little bit better with every update. Sometimes I miss the mark and just make things unnecessarily complicated without adding real value, but other times I hit on ideas that genuinely help—at least based on how I use the platform myself.
While writing code, I constantly found myself tabbing back and forth between Vercel and GitHub just to check status. To eliminate that friction, I built dedicated Vercel and GitHub integrations directly inside Pullwish. Now, your codebase status, deployments, and customer feedback live side by side. It is still a work in progress with plenty of untapped potential, but it is already saving me serious time.
One item still on my own feature backlog is expanding webhook notifications. I want instant alerts whenever a deployment fails or succeeds, when a new issue is opened on GitHub, or if a CLI process stalls. Managing those webhooks directly inside Pullwish will also let me pipe events to automated bot agents so they can triage and resolve CLI issues before I even have to lift a finger.
1. A Dedicated Vercel Workspace
You no longer need to open the Vercel console just to check if your latest commit deployed cleanly.
Pullwish now includes a full Vercel management hub under Workspace → Vercel (available on both desktop and mobile):
Deployment Overview: Monitor live deployments, build durations, commit info, and runtime frameworks at a glance.
One-Click Redeploys: Instantly trigger a redeploy directly from the dashboard if something goes wrong.
Environment Variable Management: Add, inspect, and delete environment variables across Production, Preview, and Development targets without leaving Pullwish. (For security, values remain hidden, but you can manage all variable keys).
Automatic Key Sync: Connecting your project automatically pushes your
FEATURELY_API_KEYstraight to Vercel, making SDK setup completely frictionless.
Note: The SDK packages and environment variables still use the featurely-* / FEATURELY_ prefix from before the rebrand to Pullwish. They are the current, official packages.
2. Deeper GitHub Integration
Tracking what is shipping shouldn't require jumping between browser tabs. Under Workspace → GitHub, you can now inspect your repository in real time:
Pull Requests & Commits: Track open PRs, commit history, and review progress right alongside your product roadmap.
Workflow & CI/CD Runs: See real-time pass/fail statuses for GitHub Actions runs so you know immediately when a test suite breaks.
Inline Issue Creation: Convert incoming user feedback, bug reports, or error stack traces into tracked GitHub issues with a single click.
Dependabot Integration: The Packages page now links directly to GitHub Dependabot for quick dependency updates.
3. Bi-Directional Issue Sync
When you connect your GitHub repository using a Personal Access Token (PAT), Pullwish does more than just link text.
Issues, tasks, features, and errors can be synced bidirectionally via webhooks:
Closing an issue on GitHub automatically updates the corresponding task or bug status inside Pullwish.
Reopening an issue reflects instantly on your internal Kanban board.
Public roadmap items stay updated for your users without manual data entry.
Connect Your Pipeline in Under 2 Minutes
Pullwish was built to eliminate the scattered stack. By tying customer requests and error logs directly to GitHub issues and Vercel builds, you get a unified cockpit for your entire software lifecycle.
Head over to Settings → Integrations in your dashboard to connect your GitHub repository and Vercel project today.
AI Disclaimer: The experiences and concepts shared in this article are my own. To ensure the best reading experience, I collaborated with Gemini AI to proofread my original draft, refine the sentence structure, and correct grammatical errors. No content or history was artificially generated.

