@vicoa/cli 1.3.11-linux-x64 → 1.3.11-win32-x64

package/bin/_internal/integrations/github/claude-code-action/CODE_OF_CONDUCT.md

@@ -1,128 +1,128 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-claude-code-action-coc@anthropic.com.
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+claude-code-action-coc@anthropic.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/bin/_internal/integrations/github/claude-code-action/CONTRIBUTING.md

@@ -1,116 +1,116 @@
-# Contributing to Claude Code Action
-
-Thank you for your interest in contributing to Claude Code Action! This document provides guidelines and instructions for contributing to the project.
-
-## Getting Started
-
-### Prerequisites
-
-- [Bun](https://bun.sh/) runtime
-- [Docker](https://www.docker.com/) (for running GitHub Actions locally)
-- [act](https://github.com/nektos/act) (installed automatically by our test script)
-- An Anthropic API key (for testing)
-
-### Setup
-
-1. Fork the repository on GitHub and clone your fork:
-
-   ```bash
-   git clone https://github.com/your-username/claude-code-action.git
-   cd claude-code-action
-   ```
-
-2. Install dependencies:
-
-   ```bash
-   bun install
-   ```
-
-3. Set up your Anthropic API key:
-   ```bash
-   export ANTHROPIC_API_KEY="your-api-key-here"
-   ```
-
-## Development
-
-### Available Scripts
-
-- `bun test` - Run all tests
-- `bun run typecheck` - Type check the code
-- `bun run format` - Format code with Prettier
-- `bun run format:check` - Check code formatting
-
-## Testing
-
-### Running Tests Locally
-
-1. **Unit Tests**:
-
-   ```bash
-   bun test
-   ```
-
-## Pull Request Process
-
-1. Create a new branch from `main`:
-
-   ```bash
-   git checkout -b feature/your-feature-name
-   ```
-
-2. Make your changes and commit them:
-
-   ```bash
-   git add .
-   git commit -m "feat: add new feature"
-   ```
-
-3. Run tests and formatting:
-
-   ```bash
-   bun test
-   bun run typecheck
-   bun run format:check
-   ```
-
-4. Push your branch and create a Pull Request:
-
-   ```bash
-   git push origin feature/your-feature-name
-   ```
-
-5. Ensure all CI checks pass
-
-6. Request review from maintainers
-
-## Action Development
-
-### Testing Your Changes
-
-When modifying the action:
-
-1. Test in a real GitHub Actions workflow by:
-   - Creating a test repository
-   - Using your branch as the action source:
-     ```yaml
-     uses: your-username/claude-code-action@your-branch
-     ```
-
-### Debugging
-
-- Use `console.log` for debugging in development
-- Check GitHub Actions logs for runtime issues
-- Use `act` with `-v` flag for verbose output:
-  ```bash
-  act push -v --secret ANTHROPIC_API_KEY="$ANTHROPIC_API_KEY"
-  ```
-
-## Common Issues
-
-### Docker Issues
-
-Make sure Docker is running before using `act`. You can check with:
-
-```bash
-docker ps
-```
+# Contributing to Claude Code Action
+
+Thank you for your interest in contributing to Claude Code Action! This document provides guidelines and instructions for contributing to the project.
+
+## Getting Started
+
+### Prerequisites
+
+- [Bun](https://bun.sh/) runtime
+- [Docker](https://www.docker.com/) (for running GitHub Actions locally)
+- [act](https://github.com/nektos/act) (installed automatically by our test script)
+- An Anthropic API key (for testing)
+
+### Setup
+
+1. Fork the repository on GitHub and clone your fork:
+
+   ```bash
+   git clone https://github.com/your-username/claude-code-action.git
+   cd claude-code-action
+   ```
+
+2. Install dependencies:
+
+   ```bash
+   bun install
+   ```
+
+3. Set up your Anthropic API key:
+   ```bash
+   export ANTHROPIC_API_KEY="your-api-key-here"
+   ```
+
+## Development
+
+### Available Scripts
+
+- `bun test` - Run all tests
+- `bun run typecheck` - Type check the code
+- `bun run format` - Format code with Prettier
+- `bun run format:check` - Check code formatting
+
+## Testing
+
+### Running Tests Locally
+
+1. **Unit Tests**:
+
+   ```bash
+   bun test
+   ```
+
+## Pull Request Process
+
+1. Create a new branch from `main`:
+
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. Make your changes and commit them:
+
+   ```bash
+   git add .
+   git commit -m "feat: add new feature"
+   ```
+
+3. Run tests and formatting:
+
+   ```bash
+   bun test
+   bun run typecheck
+   bun run format:check
+   ```
+
+4. Push your branch and create a Pull Request:
+
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+5. Ensure all CI checks pass
+
+6. Request review from maintainers
+
+## Action Development
+
+### Testing Your Changes
+
+When modifying the action:
+
+1. Test in a real GitHub Actions workflow by:
+   - Creating a test repository
+   - Using your branch as the action source:
+     ```yaml
+     uses: your-username/claude-code-action@your-branch
+     ```
+
+### Debugging
+
+- Use `console.log` for debugging in development
+- Check GitHub Actions logs for runtime issues
+- Use `act` with `-v` flag for verbose output:
+  ```bash
+  act push -v --secret ANTHROPIC_API_KEY="$ANTHROPIC_API_KEY"
+  ```
+
+## Common Issues
+
+### Docker Issues
+
+Make sure Docker is running before using `act`. You can check with:
+
+```bash
+docker ps
+```

package/bin/_internal/integrations/github/claude-code-action/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 Anthropic, PBC
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+MIT License
+
+Copyright (c) 2025 Anthropic, PBC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.

package/bin/_internal/integrations/github/claude-code-action/README.md

@@ -1,53 +1,53 @@
-# Vicoa GitHub Integration
-
-This integration allows you to trigger AI agents from GitHub issues, PRs, and the Vicoa dashboard to automatically respond to comments and perform code tasks.
-
-## Quick Setup Guide
-
-### Prerequisites
-
-1. **GitHub Personal Access Token (PAT)**
-   - Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
-   - Click "Generate new token (classic)"
-   - Select scopes: `repo` (full control of private repositories)
-   - Save the token securely
-
-2. **Vicoa API Key**
-   - Get your API key from the [Vicoa dashboard](https://vicoa.ai)
-   - You'll need this for webhook configuration
-
-3. **Anthropic API Key**
-   - Sign up at [Anthropic](https://console.anthropic.com)
-   - Generate an API key from your account settings
-
-### Step 1: Install the Claude Code GitHub App
-
-Visit [github.com/apps/claude-code](https://github.com/apps/claude-code) and install the app on your repository or organization.
-
-### Step 2: Add the Workflow to Your Repository
-
-1. Create `.github/workflows/vicoa.yml` in your repository
-2. Copy the workflow from [src/integrations/github/claude-code-action/examples/vicoa.yml](examples/vicoa.yml)
-3. Commit and push the file
-
-### Step 3: Configure Repository Secrets
-
-Add these secrets to your repository (Settings → Secrets and variables → Actions):
-
-- `ANTHROPIC_API_KEY`: Your Anthropic API key
-
-### Step 4: Set Up Webhook in Vicoa Dashboard
-
-1. Go to the Vicoa dashboard
-2. Create a new agent any name, and then assign it with type "GitHub Webhook"
-3. Fill in the configuration:
-   - **Repository**: `YOUR_ORG/YOUR_REPO`
-   - **PAT Token**: Your GitHub Personal Access Token
-   - **Event Type**: `vicoa-trigger`
-
-### Step 5: Launch Your Agent
-
-From the Vicoa dashboard, you can now:
-1. Click "Launch" or "+" on your configured agent
-2. Enter a prompt for the AI to execute
+# Vicoa GitHub Integration
+
+This integration allows you to trigger AI agents from GitHub issues, PRs, and the Vicoa dashboard to automatically respond to comments and perform code tasks.
+
+## Quick Setup Guide
+
+### Prerequisites
+
+1. **GitHub Personal Access Token (PAT)**
+   - Go to GitHub Settings → Developer settings → Personal access tokens → Tokens (classic)
+   - Click "Generate new token (classic)"
+   - Select scopes: `repo` (full control of private repositories)
+   - Save the token securely
+
+2. **Vicoa API Key**
+   - Get your API key from the [Vicoa dashboard](https://vicoa.ai)
+   - You'll need this for webhook configuration
+
+3. **Anthropic API Key**
+   - Sign up at [Anthropic](https://console.anthropic.com)
+   - Generate an API key from your account settings
+
+### Step 1: Install the Claude Code GitHub App
+
+Visit [github.com/apps/claude-code](https://github.com/apps/claude-code) and install the app on your repository or organization.
+
+### Step 2: Add the Workflow to Your Repository
+
+1. Create `.github/workflows/vicoa.yml` in your repository
+2. Copy the workflow from [src/integrations/github/claude-code-action/examples/vicoa.yml](examples/vicoa.yml)
+3. Commit and push the file
+
+### Step 3: Configure Repository Secrets
+
+Add these secrets to your repository (Settings → Secrets and variables → Actions):
+
+- `ANTHROPIC_API_KEY`: Your Anthropic API key
+
+### Step 4: Set Up Webhook in Vicoa Dashboard
+
+1. Go to the Vicoa dashboard
+2. Create a new agent any name, and then assign it with type "GitHub Webhook"
+3. Fill in the configuration:
+   - **Repository**: `YOUR_ORG/YOUR_REPO`
+   - **PAT Token**: Your GitHub Personal Access Token
+   - **Event Type**: `vicoa-trigger`
+
+### Step 5: Launch Your Agent
+
+From the Vicoa dashboard, you can now:
+1. Click "Launch" or "+" on your configured agent
+2. Enter a prompt for the AI to execute
 3. The agent will create a branch, make changes, and optionally create a PR if you ask it to