Feature: Custom repository actions & keyboard shortcuts
See original GitHub issueIt would be super lovely if there keyboard shortcuts for the “open” actions, so I could open a project in Windows Terminal or Windows Explorer without using the mouse when a repository is selected. Perhaps something as simple as 1
, 2
, 3
?
Happy to submit a PR for this if it’s something that you see in the vision for your project.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:21 (15 by maintainers)
Top Results From Across the Web
Keyboard shortcuts for Azure DevOps and Team Explorer
Repos files shortcuts. Shortcut, Action. 1, Open contents. 2, Open history. t, Move focus to ...
Read more >Custom actions – more power to you
SourceTree 1.3's new 'Custom Actions' feature lets you extend the ... a keyboard shortcut to open the root of the repository in TextMate?...
Read more >Repo Level Custom Actions in Toolbar
Ability to add custom actions as toolbar buttons would be lovely, at least give us the option to assign keyboard shortcuts as in...
Read more >GitLab keyboard shortcuts
Project ; t, Go to the project file search page. (Code > Repository, select Find Files). ; g + c, Go to the...
Read more >Keyboard Shortcuts
Set custom, clear, or default keyboard shortcuts by navigating to Settings > Keyboard Shortcuts . Search through the re-mappable actions using the search ......
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 FreeTop 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
Top GitHub Comments
I thought of this issue in here as I merged the PR from @henriksen as well. Just to make sure we’re talking about the same … I’d thought that the config file to define the “Open in …” actions won’t replace the whole context menu. We should keep the newly merged “Open Solution” area intact. As well as the basic git commands and the possibility to ignore repositories.
The stuff we were talking in here is indeed “Open the directory of a given repository with …”. In the sample file I added the placeholder for the
{RepositoryPath}
. But we could add more of these repository properties if they are useful. I did just not think of it yet.Another thing I thought after I merged the PR: For us Windows Devs,
*.sln
is the most used file in our repositories. But we could also make this part dynamic by adding the possibilities to define the extensions one wants to be included into the menu.This could be
… to have a menu with submenus for the matching files:
We’re going away from the initial simplicity, that’s why I struggle. However, I think the features could be very useful if the defaults are chosen wisely, like 2-3 default “Open in …” actions and the “Open Visual Studio solutions” sub menu.
I started to implement this feature a few days ago. Here’s the task list I’m working with.
(Please note that I only work on it from time to time, so progress can be slow)