[FR] Allow for restricting searches by org, repo, and branch/tag

The issue does not name files, tests, or an implementation entry point. Start by locating how search requests are handled and how GitLab repositories, organizations, and branches or tags are represented; done means searches can be restricted to each requested scope while preserving relevant source-code results.

I'd like to be able to request source code specific to projects rather than from the entire GitLab instance.

Why?

May be helpful for engineers onboarding to a team or project. It could help answer questions like "where is function xyz?", "where is this log message coming from?", etc.
Would be highly useful in agentic workflows that may analyze code or use snippets of code as part of an analysis.
- I'm thinking of a situation where you may have logs you'd like to analyze, and you know which repository or org the logs are generated from. If an agent can analyze the logs and recognize log messages that it may want to search on, narrowing the search to the specific org/repo would ensure the results are relevant, and the search may be a bit quicker.
- Example: Agent recognizes that lines 150–200 in the logs are pertinent to the failure and finds a repeating log message, ERROR something is wrong..., I want the agent to be able to search for that log message in the source code for additional targeted context rather than cloning the entire repository and flooding the context window with code.

[FR] Allow for restricting searches by org, repo, and branch/tag

Bewertung

Rechercherichtung

Beschreibung

Why?

Beitragsleitfaden

Erste Schritte

Mehr aus sourcebot-dev/sourcebot

Ähnliche Issues

[FR] Allow for restricting searches by org, repo, and branch/tag

Bewertung

Rechercherichtung

Beschreibung

Why?

Beitragsleitfaden

Erste Schritte

Mehr aus sourcebot-dev/sourcebot

Ähnliche Issues

Neue Issues direkt in Ihr Postfach