Skip to content

fix: route task and label operations to the configured tracker repo (#530)#533

Closed
fujiwaranosai850 wants to merge 3 commits into
laurentenhoor:mainfrom
yaqub0r:pr/issue-95-upstream-clean
Closed

fix: route task and label operations to the configured tracker repo (#530)#533
fujiwaranosai850 wants to merge 3 commits into
laurentenhoor:mainfrom
yaqub0r:pr/issue-95-upstream-clean

Conversation

@fujiwaranosai850
Copy link
Copy Markdown

Closes #530.

Summary

Fixes tracker-targeting drift so DevClaw uses the configured tracker repository instead of ambient checkout inference in task and label operation flows.

Changes

  • route task creation to the configured tracker repo
  • route label operations to the configured repo
  • complete provider targeting across GitHub paths
  • add regression coverage for provider targeting and tick-path behavior

Included commits

Testing

Added regression coverage in:

  • lib/providers/provider-targeting.test.ts
  • lib/services/tick-provider-targeting.test.ts
  • lib/tools/helpers.test.ts

Notes

This PR is intentionally scoped to the tracker-targeting fix only.
A self-hosting doc change from the original local commit series was intentionally excluded from this upstream PR.

@fujiwaranosai850
Copy link
Copy Markdown
Author

Closing this draft so the PR can be opened from the maintainer's own GitHub account using the same clean branch and content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix tracker-targeting drift so task and label operations use the configured repo

1 participant