domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US02-07: Automate Phase B End-to-End Acceptance #60

Merged
domverse merged 2 commits from us/US02-07-automate-phase-b-end-to-end-acceptance into main 2026-08-14 12:53:47 +02:00
Conversation 0 Commits 2 Files Changed 11 +577 -12
domverse commented 2026-08-14 12:52:57 +02:00
Owner
Copy Link

Implements #14

Tests:

  • work_item/scripts/python -m unittest discover -s work_item/tests -v
  • work_item/scripts/python -m pytest tests -q
  • work_item/scripts/python -m pytest tests/e2e -m phase_b -q

Commit: 89a7ef089bf4aa1c891339969e7b7e74a678a94e

Implements #14 Tests: - `work_item/scripts/python -m unittest discover -s work_item/tests -v` - `work_item/scripts/python -m pytest tests -q` - `work_item/scripts/python -m pytest tests/e2e -m phase_b -q` Commit: `89a7ef089bf4aa1c891339969e7b7e74a678a94e`
domverse added 2 commits 2026-08-14 12:52:57 +02:00
fix(work-item): assign issues via PATCH instead of broken sub-route ba6f41a16e 
`tea --add-assignees` posts to /issues/{n}/assignees, which returns 404 on
this Forgejo deployment and makes every `claim` fail. Set the assignee through
the issue PATCH endpoint (full assignees list), which the server accepts, and
reuse `edit_labels` for the status transition. Update the CLI e2e fake `tea`
to model the PATCH assignee call.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WMctdE9E1c8d6UHQWX8rNt
US02-07: Automate Phase B End-to-End Acceptance 89a7ef089b
domverse merged commit b9bcb47c68 into main 2026-08-14 12:53:47 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: domverse/photoanalyzer#60
Delete Branch "us/US02-07-automate-phase-b-end-to-end-acceptance"

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?