Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding more filtering to Git Repositories Browser Filter panel #16298

Open
lsafina opened this issue Mar 14, 2024 · 2 comments · May be fixed by pharo-vcs/iceberg#1817
Open

Adding more filtering to Git Repositories Browser Filter panel #16298

lsafina opened this issue Mar 14, 2024 · 2 comments · May be fixed by pharo-vcs/iceberg#1817

Comments

@lsafina
Copy link

lsafina commented Mar 14, 2024

Sometimes there are too many git repositories in Git Repositories Browser (incl. ones added by default).
It would be nice to have a possibility to see only a group of those with which one is currently working with.

Having something like '*' and '||' might help to have a basic filtering.
E.g for Moose* || FAST-JAVA* it would return the list of all repositories with names starting with either Moose or FAST-Java.

Copy link

welcome bot commented Mar 14, 2024

Thanks for opening your first issue! Please check the CONTRIBUTING documents for some tips about which information should be provided. You can find information of how to do a Pull Request here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo

GitHub
Pharo is a dynamic reflective pure object-oriented language supporting live programming inspired by Smalltalk. - pharo-project/pharo

@astares
Copy link
Member

astares commented Mar 15, 2024

Yes, a filter would be nice.

Additionally large projects like Moose could be "tagged" in the specific .project files which makes them displayed/grouped in an own tab in the iceberg repositories pane

{
	'srcDirectory' : 'src',
	'tags' : [ #moose ]
}

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 a pull request may close this issue.

2 participants