vypdev/copilot

**Copilot** is a GitHub Action for task management using Git-Flow: it links issues, branches, and pull requests to GitHub Projects, automates branch creation from labels, and keeps boards and progress in sync. Think of it as bringing Atlassian-style integration (boards, tasks, branches) to GitHub.
Full documentation: **docs.page/vypdev/copilot**
*Maintains state and configuration persisted in issue descriptions for seamless workflow automation.*
---
Documentation index
| Section | Description |
|--------|-------------|
| How to use | Step-by-step setup: PAT, copilot setup, workflows |
| Features & capabilities | Workflow triggers, single actions, agent execution, and concurrency |
| Authentication | PAT setup, permissions, token best practices |
| Configuration | All inputs: branches, labels, projects, locale, agents, and more |
| Release orchestration | Production-first release/hotfix flow, npm OIDC, reconciliation, and recovery |
| Agents | Runtime, model, CLI, policy, and failure behavior |
| Security & Operations | Credentials, trust boundaries, provisioning, verification, upgrades, and rollback |
| Development | Architecture, testing, documentation, artifacts, and release process |
---
Getting started
The recommended onboarding path is to install the published package globally with
pnpm and initialize the target repository with copilot setup:
@vypdev/copilot contains both the copilot CLI and the compiled GitHub Action.
The global installation makes the CLI and the setup templates available; it does
not install an Action into GitHub. copilot setup is the canonical initialization
flow and will, according to the selected features:
- copy the selected workflows, Issue Forms, pull request template, and repository agent guidance into the repository;
- create the labels and issue types used by the workflows;
- configure non-sensitive Repository Variables; and
- validate or provision the workflow PAT and provider credentials at the selected scope.
The wizard selects issue workflow kinds with a Space/Enter multi-select; All
is the default. It also generates .copilot/repository-profile.json,
.copilot/AGENT_GUIDE.md, and the Codex skill
.agents/skills/copilot-repository-workflow/SKILL.md by default. The generated
guidance makes clear that the Action owns remote branch lifecycle: agents work
on the exact existing branch and push normal commits, but do not create, rename,
delete, replace, or force-push managed branches.
The setup PAT entered by the operator is separate from the workflow PAT Secret.
Interactive setup can guide creation of both via GitHub's prefilled PAT form:
picks the permission-affecting setup options first, then the operator creates a temporary setup token, and the bot account creates the
persistent workflow token. GitHub handles account switching, 2FA, repository
selection, and final creation; Copilot never creates or revokes either token.
Use copilot setup --dry-run to inspect the plan before making local or remote
changes. See the complete How to use
guide and Authentication.
--web opens an ephemeral, loopback-only setup page with a six-stage progress
rail, plan review, separate masked inputs for the two PAT roles, and a
System/Light/Dark theme control. If the browser does not open, use the local
URL printed in the terminal. The page does not create PATs: GitHub owns the
form, account switch, 2FA, and token issuance. You must explicitly approve