-
Renamed
github-update-operations.js→github-actions.js- Focused on GitHub Actions operations (install, update, delete)
-
Created
github-repository.js- Repository setup and infrastructure operations
- Container directory creation
- Organization information
- Repository size checking
- Pre-flight checks for GitHub App installation
-
Created
github-companies.js- Company-specific operations
- Catch/write/release workflow demonstrations
- Sample data loading and company creation
- Company profiling capabilities
- Prerequisites checking
-
Updated
test-companies.js- Fixed process name initialization (was missing)
- Fixed file naming case sensitivity (Companies.json vs companies.json)
- Now follows proper catch/write/release pattern
- Provides observable workflow output
- Focus: Infrastructure and repository setup
- Operations:
repository- Create discovery repositorycontainers- Create container directoriesorginfo- Display organization informationreposize- Display repository size
- Features:
- GitHub App installation validation
- Existing installation detection
- User confirmation prompts
- Graceful handling of existing components
- Focus: Company data operations
- Operations:
create-test- Create first 2 test companiescreate-all- Create all remaining companieslist- List all companies with summaryprofile- Generate company profile with analytics
- Features:
- Prerequisite checking (repository, containers, sample data)
- Duplicate detection and avoidance
- Interactive company profiling
- Proper catch/write/release workflow
- Detailed workflow observability
- Process Name Issue: Fixed missing process name in Companies constructor
- File Naming: Fixed case sensitivity issue (companies.json → Companies.json)
- Branch Workflow: Now properly creates branches and writes to them (not main)
- Observable Output: Test scripts now show detailed workflow steps
- Configuration Loading: All scripts follow the same config.ini pattern
- Separation of Concerns: Repository setup vs. data operations are clearly separated
- Focused Examples: Each script has a specific purpose and clear operations
- Better User Experience: Users can run repository setup once, then focus on data operations
- Easier Debugging: Issues can be isolated to specific functionality areas
- Clearer Documentation: Each script has focused documentation and usage instructions
With this improved structure, we can now:
- Test Repository Setup: Run
node examples/github-repository.jsto set up infrastructure - Test Company Operations: Run
node examples/github-companies.jsto work with company data - Continue Debugging: Focus on the catch/write/release workflow in a clean environment
- Add More Entity Types: Easily add Studies and Interactions examples following the same pattern
The restructuring provides a much cleaner foundation for both development and user experience.