Fix: Clarify token requirements and Python dependency scope#68
Merged
Conversation
Based on user feedback, this commit addresses confusion about: 1. GitHub Token Requirements: - Emphasize that NO CONDUCTOR_GITHUB_TOKEN setup is needed - Workflows use GitHub's built-in authentication - Add clear messaging throughout installation process 2. Python Dependency Clarification: - Python is only needed for conductor scripts, NOT for CI/CD - Code Conductor does NOT add Python test/lint workflows - Language-agnostic workflows only 3. Documentation Improvements: - Add comprehensive FAQ addressing common concerns - Update installer with clearer messaging - Enhance README to highlight no-token setup This ensures users understand that Code Conductor: - Uses GitHub's built-in auth (no manual tokens) - Doesn't impose language-specific CI/CD - Only requires Python for orchestration scripts 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
Simplifies the installation process by automatically configuring all available roles instead of prompting users to select which ones they want. This change: - Removes the interactive role selection prompt - Automatically adds all 8 specialized roles during setup - Updates output messages to reflect automatic configuration - Reduces installation friction and complexity Users can simply ignore roles they don't need. Having all roles available doesn't impose any overhead and ensures maximum flexibility. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses important user feedback about confusion regarding GitHub token requirements and Python dependencies in Code Conductor. A user reported frustration about:
CONDUCTOR_GITHUB_TOKEN(which shouldn't be required)Changes Made
1. Enhanced Installation Messaging
2. Documentation Improvements
docs/FAQ.md) addressing:3. Clarified Workflow Behavior
${{ github.token }}(built-in auth)User Impact
Users will now clearly understand that:
Testing
Related Issues
Addresses user feedback about token setup confusion and Python workflow concerns.
🤖 Generated with Claude Code