Files
claude-code-action/base-action/CONTRIBUTING.md
Claude 0085208689 fix: require explicit acknowledgment for wildcard write permission bypass
SECURITY FIX: Addresses authorization_bypass vulnerability (LOW severity)

The allowed_non_write_users='*' configuration previously bypassed write
permission checks for all users with only a warning. This created a
security misconfiguration risk.

Changes:
- Added new input 'bypass_write_permission_check_acknowledgment' required
  when using wildcard (*)
- Modified checkWritePermissions() to throw error if wildcard used without
  explicit acknowledgment flag
- Updated all documentation (security.md, usage.md) with new requirement
- Updated example workflows to include acknowledgment flag
- Added tests for new validation behavior

This prevents accidental security misconfigurations while maintaining the
feature for intentional use cases like issue triage workflows.

Affected file: src/github/validation/permissions.ts:27
Category: authorization_bypass
Severity: LOW
2026-01-13 23:29:39 +00:00

2.7 KiB

Contributing to Claude Code Base Action

Thank you for your interest in contributing to Claude Code Base Action! This document provides guidelines and instructions for contributing to the project.

Getting Started

Prerequisites

  • Bun runtime
  • Docker (for running GitHub Actions locally)
  • act (installed automatically by our test script)
  • An Anthropic API key (for testing)

Setup

  1. Fork the repository on GitHub and clone your fork:

    git clone https://github.com/your-username/claude-code-base-action.git
    cd claude-code-base-action
    
  2. Install dependencies:

    bun install
    
  3. Set up your Anthropic API key:

    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:

    bun test
    
  2. Integration Tests (using GitHub Actions locally):

    ./test-local.sh
    

    This script:

    • Installs act if not present (requires Homebrew on macOS)
    • Runs the GitHub Action workflow locally using Docker
    • Requires your ANTHROPIC_API_KEY to be set

    On Apple Silicon Macs, the script automatically adds the --container-architecture linux/amd64 flag to avoid compatibility issues.

Pull Request Process

  1. Create a new branch from main:

    git checkout -b feature/your-feature-name
    
  2. Make your changes and commit them:

    git add .
    git commit -m "feat: add new feature"
    
  3. Run tests and formatting:

    bun test
    bun run typecheck
    bun run format:check
    
  4. Push your branch and create a Pull Request:

    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 locally with the test script:

    ./test-local.sh
    
  2. Test in a real GitHub Actions workflow by:

    • Creating a test repository
    • Using your branch as the action source:
      uses: your-username/claude-code-base-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:
    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:

docker ps