See GitHub Actions pipeline status directly in VS Code — no tab-switching to a browser dashboard.
Features
Status bar indicator — latest run status for your current branch (success, failure, running, pending)
Multi-repo support — see pipeline status for every GitHub repo in your workspace (multi-root workspaces supported)
Sidebar panel — recent workflow runs grouped by repository, with jobs and steps
In-editor logs — click a run, job, or step to view logs in the main editor
Failure notifications — native alert when a tracked run fails, with a link to view it
GitHub sign-in — one-click OAuth via the editor's built-in GitHub authentication
Polling — auto-refreshes every 60 seconds (configurable)
Getting started
Install Pipeline Pulse from the Marketplace
Open a workspace with a GitHub repository that has Actions enabled
Run Pipeline Pulse: Sign in with GitHub from the Command Palette
Check the status bar (bottom-left) and the Pipeline Pulse activity bar icon
Commands
Command
Description
Pipeline Pulse: Sign in with GitHub
Authenticate with GitHub
Pipeline Pulse: Sign out
Sign out and clear stored credentials
Pipeline Pulse: Refresh
Manually refresh pipeline status
Pipeline Pulse: Set Personal Access Token (Advanced)
Use a manual PAT instead of OAuth
Settings
Setting
Default
Description
pipelinePulse.pollIntervalSeconds
60
Polling interval in seconds (minimum 15)
pipelinePulse.trackBranch
current
Track current branch or repo default branch
pipelinePulse.enableNotifications
true
Notify on pipeline failure
pipelinePulse.recentRunLimit
10
Number of recent runs in the sidebar
pipelinePulse.workflowFilter
""
Show only runs whose workflow name contains this text
pipelinePulse.telemetry.enabled
false
Send anonymous usage data (opt-in)
pipelinePulse.telemetry.endpoint
""
Optional HTTPS endpoint for telemetry events
Per-repo notifications
Right-click a repository in the Pipeline Pulse sidebar → Mute Notifications / Unmute Notifications. Muted repos are remembered per workspace.
Workflow filter
Click the filter icon in the Pipeline Pulse panel toolbar, or run Pipeline Pulse: Filter Workflows from the Command Palette.
Requirements
A GitHub repository with GitHub Actions workflows
GitHub authentication with repo scope (for private repos and Actions API access)
The built-in Git extension for repository and branch detection
Known limitations
GitHub Actions only (GitLab support planned)
Logs are per-job on GitHub's API; step logs are parsed from job output
Logs may be unavailable for in-progress runs or after GitHub's retention period
Privacy
Pipeline Pulse is 100% client-side. Your credentials are stored in the editor's secret storage and API calls go directly to GitHub — no third-party servers.