[Feature Request] Additional command line arguments and commands

[littlejoe3]

https://github.com/fork-dev/TrackerWin/issues/266#issuecomment-525232996

sourcetree command line options: sourcetree [-f path] [ [] ] Commands: clone : Opens the clone dialog with the provided URL status : Opens the repository at the File Status view log : Opens the repository at the Log view search [] : Opens the repository at the Search view. If is specified, immediately searches for that text filelog : Opens the repository and then opens the log for commit : Opens the repository and immediately goes to the commit dialog

https://jira.atlassian.com/browse/SRCTREEWIN-394

fork command line options: %localappdata%\fork\fork.exe /absolute/path/to/repo

is there any chance to CLI commands like filelog? %localappdata%\fork\fork.exe /absolute/path/to/repo filelog /path/to/file

[ta32]

Also please add an option for opening the blame timeline on a specific file.

Once the command line options are there it would be easy for people to make changes to their registry and change the explorer context menu options like in https://github.com/fork-dev/TrackerWin/issues/89

[ndarlington]

If Fork had a command line argument for accepting a url to clone as described above, we would also have the agency to be able to solve the "Open in Sourcetree" link in Bitbucket issues too (by creating a url protocol handler app for the sourcetree:// protocol, and passing the clone url from it to a fork command line argument).

[adevaykin]

This would also allow context menu integration for Mac users. It is now a big pain to show blame in Fork for a specific file in Finder.

[DanPristupov]

@adevaykin Use Cmd+P -> Blame -> filename. Same works for file history

[adevaykin]

Thank you @DanPristupov ! Fine as a workaround, still shell integration would be great.

[ghost]

@adevaykin Use Cmd+P -> Blame -> filename. Same works for file history

after you repeat this 100 times a day, you can apply to psychiatry due to brain trauma. tools should speed up (automate) actions, not turn people into machines that repeat monotonous actions.

[DanPristupov]

@dick2tick what do you propose instead? How can we open blame for a particular file faster?

[ghost]

developers usually use some IDE to edit the code and currently there is no good integration between those tools and fork, but with the ability to run file history or blame from the command line the work can be automated (with the mentioned command line arguments and commands @littlejoe3, only one click or shortcut will be needed to display blame or filelog from IDE).

I would definitely like to speed up the unnecessary typing: Cmd+P -> Blame -> filename because I pressed those keys so many times that they wore out.

[Otiel]

Same request #997

[AndrewGodfrey]

Me too. I have an editor integration that opens git history on a file, or on the selected range of lines in the file. Currently that uses gitk. I would much prefer to use Fork's history window, but since I can't access it from there, gitk it remains. This integration predates my use of git - I used to use Mercurial a lot, and I used TortoiseHg's history for that. The point being: This is bigger than Fork.