Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Selecting repository does not clear the filter text
See original GitHub issueDescription
- Click ‘Current repository’ button and type some filter text
- Select the repository
- Click ‘Current repository’ again
Version
- GitHub Desktop: 1.1.0
- Operating system: Windows 10 RS3
Steps to Reproduce
Expected Behavior
The filter text should disappear, as it did in 0.5.3
Actual Behavior
The filter text still exists, I have to delete it to select another repo
Additional Information
Logs
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
git-filter-repo command man page - ManKier
Rapidly rewrite entire repository history using user-specified filters. This is a destructive operation which should not be used lightly; it writes new ...
Read more >Reduce repository size - GitLab Docs
Rewriting a repository can remove unwanted history to make the repository smaller. We recommend git filter-repo over git filter-branch and BFG.
Read more >Clear or remove a filter - Microsoft Support
There are several options: Clear a filter from a specific column. Clear all filters.
Read more >List and filter your resources - Amazon Elastic Compute Cloud
Note that not all screens support editing the selected filter. Edit a filter. When you are finished, remove the filter. ... InstanceId" --output...
Read more >Searching and filtering - Perforce
Click the Clear filter p4v clearfilters icon or go to the Search menu and select Clear <spec type>Filter. Filter with file paths. You...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I agree with @saschanaz from the perspective that the current experience is optimized for those that navigate this flow via the keyboard at the expense of the person using the mouse. If I have previously filtered my repositories and successfully found the repo I wanted and want to find another one but don’t remember the name of it, I have to click the tiny target of the ❌ to clear the filter before continuing. This is a much more cumbersome flow than it is in the keyboard scenario.
A compromise is a compromise, I hate when I click “Current repository” with my mouse and then it forces me to tap my keyboard button. My local repositories have their unique names, no need to keep search results.