vypdev/Copilot - Github with super powers
Automates branch management, GitHub project linking, and issue/PR tracking with Git-Flow methodology.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| debug | Enable debug mode. | — | false |
| single-action | Launch single actions. | — | "" |
| single-action-issue | Issue target for executing single action. | — | "" |
| single-action-version | Version target for executing single action. | — | "" |
| single-action-title | Title target for executing single action. | — | "" |
| single-action-changelog | Changelog target for executing single action. | — | "" |
| emoji-labeled-title | Enable titles with emojis based on issue labels. | — | true |
| branch-management-launcher-label | Label to trigger branch management actions. | — | branched |
| branch-management-always | If true, ignores the branch-management-launcher-label requirement for running Git Board. | — | false |
| branch-management-emoji | Emoji to indicate branched issues. It will be ignored if emoji-labeled-title is false. | — | 🧑💻 |
| docs-label | Label to manage docs branches. | — | docs |
| documentation-label | Label to manage docs branches. | — | documentation |
| chore-label | Label to manage chore branches. | — | chore |
| maintenance-label | Label to manage chore branches. | — | maintenance |
| hotfix-label | Label to manage hotfix branches. | — | hotfix |
| release-label | Label to manage release branches. | — | release |
| bug-label | Label to indicate a bug type. | — | bug |
| bugfix-label | Label to manage bugfix branches. | — | bugfix |
| feature-label | Label to manage feature branches. | — | feature |
| enhancement-label | Label to indicate a enhancement type. | — | enhancement |
| question-label | Label to detect issues marked as questions. | — | question |
| help-label | Label to detect help request issues. | — | help |
| deploy-label | Label to detect deploy actions. | — | deploy |
| deployed-label | Label to detect the deployed was. | — | deployed |
| priority-high-label | Label to indicate a priority high. | — | priority: high |
| priority-medium-label | Label to indicate a priority medium. | — | priority: medium |
| priority-low-label | Label to indicate a priority low. | — | priority: low |
| priority-none-label | Label to indicate no priority. | — | priority: none |
| size-xxl-label | Label to indicate a task of size XXL. | — | size: XXL |
| size-xl-label | Label to indicate a task of size XL. | — | size: XL |
| size-l-label | Label to indicate a task of size L. | — | size: L |
| size-m-label | Label to indicate a task of size M. | — | size: M |
| size-s-label | Label to indicate a task of size S. | — | size: S |
| size-xs-label | Label to indicate a task of size XS. | — | size: XS |
| size-xxl-threshold-lines | Threshold for size XXL in lines. | — | 1000 |
| size-xxl-threshold-files | Threshold for size XXL in files. | — | 20 |
| size-xxl-threshold-commits | Threshold for size XXL in commits. | — | 10 |
| size-xl-threshold-lines | Threshold for size XL in lines. | — | 500 |
| size-xl-threshold-files | Threshold for size XL in files. | — | 10 |
| size-xl-threshold-commits | Threshold for size XL in commits. | — | 5 |
| size-l-threshold-lines | Threshold for size L in lines. | — | 250 |
| size-l-threshold-files | Threshold for size L in files. | — | 5 |
| size-l-threshold-commits | Threshold for size L in commits. | — | 3 |
| size-m-threshold-lines | Threshold for size M in lines. | — | 100 |
| size-m-threshold-files | Threshold for size M in files. | — | 3 |
| size-m-threshold-commits | Threshold for size M in commits. | — | 2 |
| size-s-threshold-lines | Threshold for size S in lines. | — | 50 |
| size-s-threshold-files | Threshold for size S in files. | — | 2 |
| size-s-threshold-commits | Threshold for size S in commits. | — | 1 |
| size-xs-threshold-lines | Threshold for size XS in lines. | — | 25 |
| size-xs-threshold-files | Threshold for size XS in files. | — | 1 |
| size-xs-threshold-commits | Threshold for size XS in commits. | — | 1 |
| project-ids | Comma-separated list of project IDs to link issues and pull requests. | — | "" |
| project-column-issue-created | Name of the project column for new issues. | — | Todo |
| project-column-pull-request-created | Name of the project column for new pull requests. | — | In Progress |
| project-column-issue-in-progress | Name of the project column for in progress issues. | — | In Progress |
| project-column-pull-request-in-progress | Name of the project column for in progress pull requests. | — | In Progress |
| issue-type-task | Name of the issue type for tasks. | — | Task |
| issue-type-task-description | Description of the issue type for tasks. | — | A specific piece of work or activity that needs to be completed to achieve project goals. |
| issue-type-task-color | Color of the issue type for tasks. | — | blue |
| issue-type-bug | Name of the issue type for bugs. | — | Bug |
| issue-type-bug-description | Description of the issue type for bugs. | — | An issue indicating a defect, error, or malfunction that needs to be investigated and fixed. |
| issue-type-bug-color | Color of the issue type for bugs. | — | orange |
| issue-type-feature | Name of the issue type for features. | — | Feature |
| issue-type-feature-description | Description of the issue type for features. | — | A new functionality, enhancement, or improvement requested for the project. |
| issue-type-feature-color | Color of the issue type for features. | — | green |
| issue-type-documentation | Name of the issue type for documentation. | — | Documentation |
| issue-type-documentation-description | Description of the issue type for documentation. | — | An update, addition, or correction needed in the project's documentation. |
| issue-type-documentation-color | Color of the issue type for documentation. | — | pink |
| issue-type-maintenance | Name of the issue type for maintenance. | — | Maintenance |
| issue-type-maintenance-description | Description of the issue type for maintenance. | — | A task related to refactoring, dependency updates, or other technical maintenance work. |
| issue-type-maintenance-color | Color of the issue type for maintenance. | — | purple |
| issue-type-hotfix | Name of the issue type for hotfixes. | — | Hotfix |
| issue-type-hotfix-description | Description of the issue type for hotfixes. | — | A quick and urgent fix applied to resolve a critical issue in production. |
| issue-type-hotfix-color | Color of the issue type for hotfixes. | — | red |
| issue-type-release | Name of the issue type for releases. | — | Release |
| issue-type-release-description | Description of the issue type for releases. | — | An issue representing a deployment or version release of the project. |
| issue-type-release-color | Color of the issue type for releases. | — | yellow |
| issue-type-question | Name of the issue type for questions. | — | Question |
| issue-type-question-description | Description of the issue type for questions. | — | A question or clarification request related to the project or its implementation. |
| issue-type-question-color | Color of the issue type for questions. | — | gray |
| issue-type-help | Name of the issue type for help. | — | Help |
| issue-type-help-description | Description of the issue type for help. | — | A request for support, guidance, or assistance regarding the project. |
| issue-type-help-color | Color of the issue type for help. | — | purple |
| issues-locale | Locale of the issues. | — | en-US |
| pull-requests-locale | Locale of the pull requests. | — | en-US |
| main-branch | Name of the main branch (e.g., master). | — | master |
| development-branch | Name of the development branch (e.g., develop). | — | develop |
| docs-tree | Naming convention for docs branches. | — | docs |
| chore-tree | Naming convention for chore branches. | — | chore |
| feature-tree | Naming convention for feature branches. | — | feature |
| bugfix-tree | Naming convention for bugfix branches. | — | bugfix |
| hotfix-tree | Naming convention for hotfix branches. | — | hotfix |
| release-tree | Naming convention for release branches. | — | release |
| images-on-issue | Include images in issue comments. | — | true |
| images-on-pull-request | Include images in pull request comments. | — | true |
| images-on-commit | Include images in commit comments. | — | true |
| images-issue-automatic | Image URLs to display in automatic action issue comments. | — | "" |
| images-issue-feature | Image URLs to display in feature action issue comments. | — | "" |
| images-issue-bugfix | Image URLs to display in bugfix action issue comments. | — | "" |
| images-issue-docs | Image URLs to display in docs action issue comments. | — | "" |
| images-issue-chore | Image URLs to display in chore action issue comments. | — | "" |
| images-issue-hotfix | Image URLs to display in hotfix action issue comments. | — | "" |
| images-issue-release | Image URLs to display in release action issue comments. | — | "" |
| images-pull-request-automatic | Image URLs to display in automatic action pull request comments. | — | "" |
| images-pull-request-feature | Image URLs to display in feature action pull request comments. | — | "" |
| images-pull-request-bugfix | Image URLs to display in bugfix action pull request comments. | — | "" |
| images-pull-request-docs | Image URLs to display in docs action pull request comments. | — | "" |
| images-pull-request-chore | Image URLs to display in chore action pull request comments. | — | "" |
| images-pull-request-hotfix | Image URLs to display in hotfix action pull request comments. | — | "" |
| images-pull-request-release | Image URLs to display in release action pull request comments. | — | "" |
| images-commit-feature | Image URLs to display in feature action commit comments. | — | "" |
| images-commit-bugfix | Image URLs to display in bugfix action commit comments. | — | "" |
| images-commit-release | Image URLs to display in release action commit comments. | — | "" |
| images-commit-automatic | Image URLs to display in automatic action commit comments. | — | "" |
| images-commit-docs | Image URLs to display in docs action commit comments. | — | "" |
| images-commit-chore | Image URLs to display in chore action commit comments. | — | "" |
| images-commit-hotfix | Image URLs to display in hotfix action commit comments. | — | "" |
| commit-prefix-transforms | List of transformations to apply sequentially for commit prefix generation. Options: replace-slash, replace-all, lowercase, uppercase, kebab-case, snake-case, camel-case, trim, remove-numbers, clean-dashes, etc. | — | replace-slash |
| reopen-issue-on-push | Reopens a closed issue when changes are pushed to the branch associated with the issue. | — | true |
| release-workflow | Release workflow for running release deploys. | — | release_workflow.yml |
| hotfix-workflow | Hotfix workflow for running hotfix deploys. | — | hotfix_workflow.yml |
| desired-assignees-count | The number of assignees desired for the issue or pull request. If set to 0, no assignees will be added. If the number exceeds the available members, all members will be assigned. Max 10. | — | 1 |
| desired-reviewers-count | The number of reviewers desired for the pull request. If set to 0, no reviewers will be added. If the number exceeds the available members, all members will be reviewers. Max 15. | — | 1 |
| merge-timeout | The timeout for the merge workflow in seconds. If set to 0, the merge will not be timed out. | — | 600 |
| token | Fine-grained personal access token for branch and project operations | yes | — |
| opencode-server-url | OpenCode server URL for AI operations (e.g. http://localhost:4096). OpenCode supports 75+ LLM providers. | — | http://localhost:4096 |
| opencode-model | OpenCode model in provider/model format (default opencode/kimi-k2.5-free; e.g. openai/gpt-4o-mini). | — | opencode/kimi-k2.5-free |
| opencode-start-server | If true, the action starts an OpenCode server at the beginning and stops it when the job ends. No need to install or run OpenCode yourself. Requires provider API keys as secrets (e.g. OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY) passed via env. | — | true |
| ai-pull-request-description | Enable AI-powered automatic updates for pull request descriptions. | — | true |
| ai-ignore-files | Comma-separated list of files to ignore for AI operations. | — | "" |
| ai-members-only | Restrict AI features to only organization/project members. | — | false |
| ai-include-reasoning | Include reasoning or chain-of-thought in AI responses when supported by the model. | — | true |
| bugbot-severity | Minimum severity for potential-problem detections to be published (info, low, medium, high). Findings below this are not posted as comments. | — | low |
| bugbot-comment-limit | Maximum number of potential-problem findings to publish as individual comments on the issue and PR. Extra findings are summarized in a single overflow comment. | — | 20 |
| bugbot-fix-verify-commands | Comma-separated commands to run after bugbot autofix (e.g. npm run build, npm test, npm run lint). OpenCode runs these in its workspace; the runner can re-run them before commit. If empty, only OpenCode's run is used. | — | "" |
Outputs
no outputs