[Fleet Execution] [GitHub Actions Example]

[davideast]

Goal Reference

This issue was generated from .fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.

Objective

Create an example demonstrating the use of the Jules SDK within a GitHub Action. This will showcase event-driven or scheduled workflows using Jules directly in CI/CD.

Code-Level Diagnosis

Code path: packages/core/examples/github-actions/
Mechanism: The packages/core/examples/github-actions/ directory and its corresponding examples are entirely missing.
Root cause: The SDK lacks a runnable, practical example of integrating Jules with GitHub Actions workflows.

Current Implementation

# Missing example

Proposed Implementation

Files to modify: Create packages/core/examples/github-actions/index.ts, packages/core/examples/github-actions/action.yml, and packages/core/examples/github-actions/README.md. Update packages/core/README.md to link to the new example.

Integration (Before -> After)

--- a/packages/core/README.md
+++ b/packages/core/README.md
@@ -10,6 +10,10 @@
 Orchestrate complex, long-running coding tasks to an ephemeral cloud environment integrated with a GitHub repo.
 
+## Examples
+
+- [Basic Session](./examples/basic-session/README.md)
+- [Advanced Session](./examples/advanced-session/README.md)
+- [Agent Workflow](./examples/agent/README.md)
+- [Webhook Integration](./examples/webhook/README.md)
+- [GitHub Actions](./examples/github-actions/README.md)
+
 ## Send work to a Cloud based session

Test Scenarios

1. The example contains valid TypeScript and a well-formed GitHub Action YAML.
2. Follow the README.md instructions -> Instructions correctly guide a user to implement the GitHub action in their repository.

Target Files

• packages/core/examples/github-actions/index.ts
• packages/core/examples/github-actions/action.yml
• packages/core/examples/github-actions/README.md
• packages/core/examples/github-actions/package.json
• packages/core/README.md

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.

---

Fleet Context

• Source: jules:session:14691557552061927599
• Link: https://jules.google.com/session/14691557552061927599