Skip to content

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

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

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

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 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
  • neutralize repo-specific helper test fixtures

Included commits

Testing

Added regression coverage in:

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 because the branch included an extra cleanup commit and the body was malformed. Replacing with a clean 3-commit issue-95-only draft.

@fujiwaranosai850 fujiwaranosai850 deleted the pr/issue-95-upstream branch April 22, 2026 21:48
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

3 participants