mirror of
https://github.com/github/awesome-copilot.git
synced 2026-02-22 11:25:13 +00:00
Add iterative RALPH-loop (Read, Act, Log, Persist, Halt) pattern implementations for all four supported languages: - C#/.NET: ralph-loop.cs with documentation - Node.js/TypeScript: ralph-loop.ts with documentation - Python: ralph_loop.py with documentation (async API) - Go: ralph-loop.go with documentation Each recipe demonstrates: - Self-referential iteration where AI reviews its own output - Completion promise detection to halt the loop - Max iteration safety limits - File persistence between iterations Verified against real Copilot SDK APIs: - Python: fully verified end-to-end with github-copilot-sdk - Node.js: fully verified end-to-end with @github/copilot-sdk - C#: compiles and runs successfully with GitHub.Copilot.SDK - Go: compiles against github.com/github/copilot-sdk/go v0.1.23
Runnable Recipe Examples
This folder contains standalone, executable Go examples for each cookbook recipe. Each file is a complete program that can be run directly with go run.
Prerequisites
- Go 1.21 or later
- GitHub Copilot SDK for Go
go get github.com/github/copilot-sdk/go
Running Examples
Each .go file is a complete, runnable program. Simply use:
go run <filename>.go
Available Recipes
| Recipe | Command | Description |
|---|---|---|
| Error Handling | go run error-handling.go |
Demonstrates error handling patterns |
| Multiple Sessions | go run multiple-sessions.go |
Manages multiple independent conversations |
| Managing Local Files | go run managing-local-files.go |
Organizes files using AI grouping |
| PR Visualization | go run pr-visualization.go |
Generates PR age charts |
| Persisting Sessions | go run persisting-sessions.go |
Save and resume sessions across restarts |
Examples with Arguments
PR Visualization with specific repo:
go run pr-visualization.go -repo github/copilot-sdk
Managing Local Files (edit the file to change target folder):
# Edit the targetFolder variable in managing-local-files.go first
go run managing-local-files.go
Go Best Practices
These examples follow Go conventions:
- Proper error handling with explicit checks
- Use of
deferfor cleanup - Idiomatic naming (camelCase for local variables)
- Standard library usage where appropriate
- Clean separation of concerns