mirror of
https://github.com/Sea-Haven-Industries/open-swe.git
synced 2026-09-30 19:43:15 +00:00
e215f1ef8d
A user mention of "what the default repo is?" was being parsed by the `repo[: ]([a-zA-Z0-9_.\-/]+)` regex in `extract_repo_from_text`: the space form matched "repo is" and captured "is" as the repo name, which combined with the default owner to silently route the run to `langchain-ai/is`. The user's profile `default_repo` was never reached because the regex short-circuited first. The freeform extraction was solving a problem that user-level config already handles better: * Slack thread metadata carries the repo across follow-up mentions. * Dashboard profile `default_repo` is per-user and explicit. * Linear team/project mapping handles per-team routing. * GitHub webhooks know the repo from the payload — no parsing needed. So `extract_repo_from_text` and its tests are gone. `get_slack_repo_config` and the Linear webhook now fall through: thread metadata (Slack) → user profile → env / team-mapping defaults. Users who want a one-off override update their dashboard profile or post in a thread that's already on the target repo. Obsolete tests removed; `test_get_slack_repo_config_uses_thread_metadata_when_set` added to cover the remaining "thread metadata wins" path. |
||
|---|---|---|
| .. | ||
| dashboard | ||
| integrations | ||
| middleware | ||
| tools | ||
| utils | ||
| encryption.py | ||
| prompt.py | ||
| reviewer.py | ||
| reviewer_diff.py | ||
| reviewer_findings.py | ||
| reviewer_publish.py | ||
| server.py | ||
| webapp.py | ||