You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I found in the Info.plist scheme, Forkapp supports handling a custom HTTP scheme (also known as deeplinking) named forkapp. I am used to automating many common actions on my Stream Deck device, so I'd like to do something similar for Fork.
Example: I would like to bind different forkapp: URLs to Stream Deck keys to bring the app to the front and open/focus on a specific repository (for example, by providing the path to the repository as part of that URL).
Unfortunately, I couldn't find any documentation regarding the forkapp HTTP scheme, so I'm unsure if it is possible or how to achieve such functionality through deeplinks. Have you considered creating such documentation, or is that HTTP scheme not yet implemented in the app (perhaps it is used only internally for OAuth2 callbacks)? I think documenting it in the https://github.com/fork-dev/Docs repo would be sufficient.
The text was updated successfully, but these errors were encountered:
As I found in the Info.plist scheme, Forkapp supports handling a custom HTTP scheme (also known as deeplinking) named
forkapp
. I am used to automating many common actions on my Stream Deck device, so I'd like to do something similar for Fork.Example: I would like to bind different
forkapp:
URLs to Stream Deck keys to bring the app to the front and open/focus on a specific repository (for example, by providing the path to the repository as part of that URL).Unfortunately, I couldn't find any documentation regarding the
forkapp
HTTP scheme, so I'm unsure if it is possible or how to achieve such functionality through deeplinks. Have you considered creating such documentation, or is that HTTP scheme not yet implemented in the app (perhaps it is used only internally for OAuth2 callbacks)? I think documenting it in the https://github.com/fork-dev/Docs repo would be sufficient.The text was updated successfully, but these errors were encountered: