Add global filter across repos

[FisherSkyi]

What feature(s) would you like to see in RepoSense

We need a global filter that filter across all authors/repos and display that new view in code panel on the right side.

Currently we only have a local searching filter that filter across one single author after click </> to get into code panel.

Screen.Recording.2026-01-18.at.10.54.34.PM.mov

Is the feature request related to a problem?

Students in SWE course might want to see globally how other student code out a certain file e.g. testing, **/ug.md, etc

We have break down by file type but user may want to self define the type to be shown.

If possible, describe the solution

Use the input box on the left side to do global search and the one on the left to do local search.

If applicable, describe alternatives you've considered

Additional context

• we may also update the charts after the global search
• this may increase the lagging.

[FisherSkyi]

@jonasongg @lyuanww Could you take a look at this issue when you have a chance? What do you think would be the best way to handle it?

[jonasongg]

@FisherSkyi can i check what this feature would entail? does that mean if i search in the global filter, only those commits containing that file will appear in the summary chart?

[FisherSkyi]

@jonasongg yes and we might need to update both

• the summary charts (by only showing the commit containing matching files)
• AND the code panel on the right half to show ALL files across repos that match this filtering pattern
  For example, if both team-A and team-B's tp repos contain file README.md, then search **/README.md should render change in both team-A's readme and team-B's readme in the code panel. Right now this is not achievable as we can only view the file change in single repo as a "local search".

[jonasongg]

@FisherSkyi ah i see. i think the second change (code panel) might be a bigger one then, because right now if i'm not wrong, it's meant to only show the code for one repo at a time. @lyuanww @damithc what do you think about this proposed change?

[lyuanww]

@FisherSkyi Global search seems like a useful feature. However, if we want to filter by file purpose (e.g., testing-related files), it might not be too effective since we use globs (file names/types).

Regarding the second change (the code panel on the right), I agree with @jonasongg that this would likely be a larger effort. It’s important to preserve the current functionality of the code panel. I guess one possible approach could be allowing users to toggle between the code panel and the global search panel.

[FisherSkyi]

However, if we want to filter by file purpose (e.g., testing-related files), it might not be too effective since we use globs (file names/types).

I agree that in real working scenario, glob might not be the best way for product managers to monitor progress.
But from CS2103T student' point of view, they may find being able to search for AddCommand.java or *Command.java of fellow students' submission useful while developing ip/tp since they can make comparison between different approaches.

I guess one possible approach could be allowing users to toggle between the code panel and the global search panel.

Yes this seems a great way to keep current functionality while developing global search.