Onboarding Guide
Permission Requirement
Platform Admin role
Prerequisites
Before creating your first Vibe-Shift pipeline, confirm the following:
An Opsera account.
A GitHub, GitLab, or Bitbucket repository containing your vibe-coded app
A GitHub Personal Access Token with the following scopes:
repo— full repository accessadmin:repo_hook— webhook registration for auto-deploy
Note on token scopes: Your GitHub PAT must include both
repoandadmin:repo_hook. Withoutadmin:repo_hook, the GitOps webhook cannot be registered and pushes tomainwill not trigger the pipeline automatically.
Create Your First Vibe-Shift Pipeline

Follow these steps to go from a Git repo to a deployed production app.
Step 3 — Create a new pipeline
Click + New Vibe-Shift Pipeline in the top right. Enter a pipeline name (e.g. Task Management App). Choose your authentication method:
Personal Access Token (recommended) — paste your GitHub PAT
GitHub App — use if your org enforces GitHub App auth
Required scopes: repo, admin:repo_hook. Click Next.
Search your repositories from the dropdown, or paste the repo URL directly. Then set:
Branch — default is
mainApp Name — becomes the deployed container/app identifier
Environment — select
devorprod
Auto-deploy is enabled by default. A GitHub webhook is registered automatically — every push to main triggers the full pipeline without any manual action. Expand Advanced Options for additional configuration if needed. Click Create.
View the Vibe-Shift Dashboard
Once your pipeline is created, it kicks off automatically. Here is how to read the interface:
The Execution View (Pipeline Flow)
The Insights View (Analytics)
Last updated

