syntaqxThe desktop app has developer tools: a Developer tools setting, off unless someone turns it on under Window in the app's settings, lets F12 on the page, Ctrl+Shift+I (⌥⌘I on macOS) and the View menu's new Developer tools row open the web inspector for the site's page, so a page that says something went wrong can be looked into from its console. Release builds have the inspector through Tauri's devtools feature, which on macOS reaches it through WebKit's private API, so the app could not go in the Mac App Store; it ships from g1t.sh. With the setting off none of these open it, and the menu row is greyed out. On Windows the setting takes effect at once, WebView2's own F12, Ctrl+Shift+I and Inspect following it; WebKit on macOS and Linux keeps what the page's web view was made with, so there the settings offer Restart now, as they do for the title bar. The site can open it too, through window.g1tDesktop.devtools.open(), a new open_devtools command that answers only the server's page in the window and only while the setting is on, granted to the server's origin alone. The settings window and the Runner window keep the setting when they save, and the desktop app guide says how to turn it on and open it.844621cHistory
README.md
GitHub's workflow schema
workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from
actions/languageservices, file
workflow-parser/src/workflow-v1.0.json, at commit
4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed;
LICENSE is that repository's licence, copied from the same commit.
g1t does not read it at run time. src/syntax.rs lists the keys each part of a
workflow may have, and its tests check those lists against this file, so they
cannot drift from GitHub's. To update it, copy the file again, write the commit
here, and run cargo test -p g1t-actions.