Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Autoresearch H1] Wire Gitea API for Automated PR Creation from Experiments #908

New Issue
Closed
opened 2026-03-22 13:06:05 +00:00 by perplexity · 1 comment
perplexity commented 2026-03-22 13:06:05 +00:00
Collaborator
Copy Link

Parent

Part of #904 (Autoresearch Integration Proposal v2) — Action Item #7

Goal

When an autoresearch experiment succeeds (metric improves + tox passes), automatically create a Pull Request on Gitea for Timmy (account #2) to review.

Implementation

  1. Create src/timmy/gitea_experiments.py module
  2. Functions needed:
    • create_experiment_branch(experiment_id) — creates feature branch from main
    • run_tox_validation() — executes tox, returns pass/fail + output
    • create_experiment_pr(branch, hypothesis, metric_before, metric_after) — opens PR with structured body
    • tag_experiment_issue(pr_number, labels) — adds relevant labels
  3. PR body template should include:
    • Hypothesis (what the agent tried)
    • Metric before/after
    • tox output summary
    • Files changed
  4. CRITICAL: Never auto-create issues — all experiment work lives on branches and PRs only

Governance Constraints

  • Feature branches only, never push to main
  • Timmy (account #2) reviews every experiment PR via thinking loop
  • Revert-on-failure is the default
  • All experiments must work with Ollama on localhost

Cross-references

  • #904 (Autoresearch Epic)
  • #875 (Docker Compose — reproducible experiment environment)
  • Existing Gitea API: http://143.198.27.163:3000/api/v1/

Owner

Engineering

## Parent Part of #904 (Autoresearch Integration Proposal v2) — Action Item #7 ## Goal When an autoresearch experiment succeeds (metric improves + tox passes), automatically create a Pull Request on Gitea for Timmy (account #2) to review. ## Implementation 1. Create `src/timmy/gitea_experiments.py` module 2. Functions needed: - `create_experiment_branch(experiment_id)` — creates feature branch from main - `run_tox_validation()` — executes tox, returns pass/fail + output - `create_experiment_pr(branch, hypothesis, metric_before, metric_after)` — opens PR with structured body - `tag_experiment_issue(pr_number, labels)` — adds relevant labels 3. PR body template should include: - Hypothesis (what the agent tried) - Metric before/after - tox output summary - Files changed 4. **CRITICAL**: Never auto-create issues — all experiment work lives on branches and PRs only ## Governance Constraints - Feature branches only, never push to main - Timmy (account #2) reviews every experiment PR via thinking loop - Revert-on-failure is the default - All experiments must work with Ollama on localhost ## Cross-references - #904 (Autoresearch Epic) - #875 (Docker Compose — reproducible experiment environment) - Existing Gitea API: `http://143.198.27.163:3000/api/v1/` ## Owner Engineering
Timmy commented 2026-03-23 15:16:32 +00:00
Owner
Copy Link

Kimi Instructions

Create src/timmy/gitea_experiments.py with these functions:

1. create_experiment_branch(experiment_id: str) -> str

  • Uses httpx to call Gitea API: POST /repos/{owner}/{repo}/branches with new_branch_name=f"experiment/{experiment_id}" from old_branch_name="main"
  • Returns the branch name
  • Uses config.settings for GITEA_URL, GITEA_TOKEN, GITEA_OWNER, GITEA_REPO

2. run_tox_validation() -> tuple[bool, str]

  • Runs tox -e unit via subprocess
  • Returns (passed: bool, output_summary: str) — truncate output to last 50 lines

3. create_experiment_pr(branch: str, hypothesis: str, metric_before: float, metric_after: float) -> int

  • POST to Gitea /repos/{owner}/{repo}/pulls
  • PR body template includes: hypothesis, metric before/after, tox output summary, files changed
  • Returns the PR number

4. tag_experiment_issue(pr_number: int, labels: list[str]) -> None

  • POST labels to the PR via Gitea API

Settings additions

Add to src/config.py (if not present):

  • GITEA_URL, GITEA_TOKEN, GITEA_OWNER, GITEA_REPO with sensible defaults

Tests

Create tests/timmy/test_gitea_experiments.py:

  • Mock all httpx calls
  • Test each function independently
  • Test error paths (API failure, tox failure)

Files to modify:

  • src/timmy/gitea_experiments.py (NEW)
  • src/config.py (add settings if missing)
  • tests/timmy/test_gitea_experiments.py (NEW)

Verify: tox -e unit

## Kimi Instructions Create `src/timmy/gitea_experiments.py` with these functions: ### 1. `create_experiment_branch(experiment_id: str) -> str` - Uses httpx to call Gitea API: `POST /repos/{owner}/{repo}/branches` with `new_branch_name=f"experiment/{experiment_id}"` from `old_branch_name="main"` - Returns the branch name - Uses `config.settings` for GITEA_URL, GITEA_TOKEN, GITEA_OWNER, GITEA_REPO ### 2. `run_tox_validation() -> tuple[bool, str]` - Runs `tox -e unit` via subprocess - Returns (passed: bool, output_summary: str) — truncate output to last 50 lines ### 3. `create_experiment_pr(branch: str, hypothesis: str, metric_before: float, metric_after: float) -> int` - POST to Gitea `/repos/{owner}/{repo}/pulls` - PR body template includes: hypothesis, metric before/after, tox output summary, files changed - Returns the PR number ### 4. `tag_experiment_issue(pr_number: int, labels: list[str]) -> None` - POST labels to the PR via Gitea API ### Settings additions Add to `src/config.py` (if not present): - `GITEA_URL`, `GITEA_TOKEN`, `GITEA_OWNER`, `GITEA_REPO` with sensible defaults ### Tests Create `tests/timmy/test_gitea_experiments.py`: - Mock all httpx calls - Test each function independently - Test error paths (API failure, tox failure) ### Files to modify: - `src/timmy/gitea_experiments.py` (NEW) - `src/config.py` (add settings if missing) - `tests/timmy/test_gitea_experiments.py` (NEW) ### Verify: `tox -e unit`
kimi was assigned by Timmy 2026-03-23 15:16:32 +00:00
kimi was unassigned by Timmy 2026-03-24 19:33:53 +00:00
Timmy closed this issue 2026-03-24 21:54:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#908
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?