Archives

Creating databases for Ruby requires no additional dependencies. In the command line you must specify --language=ruby. For example: codeql database create --language=ruby --source-root <folder-to-extract> <output-folder>/ruby-database Here, we have specified a --source-root path, which is the location where database creation is executed, but is not necessarily the checkout root of the codebase

On your Mac, click the Input menu in the menu bar, then choose Show Keyboard Viewer.

~/Users/user/Library/com.pieces.os/production/Pieces

curl

Notebooks are like runbooks that live next to your command line in the terminal. They’re easy to find, run, and edit. Every Notebook can include executable commands or Workflows, so you can step through multi-step playbooks without copy, pasting, or context-switching. Plus, you can export Notebooks in Markdown format, so there’s no lock in.

Teams that want to centralize their docs might adopt a browser-based documentation solution. These apps move the docs further away from where engineers are getting work done. It’s a long journey to the browser with ample room for distractions. If you manage to locate the right doc, you still have to copy / paste the commands into your terminal, slowing you down at every step. If you find content that’s out-of-date, you have to completely stop what you’re doing to go make a change.

If you ever need to edit a shared Workflow because the right command for a tool or process changed, you can make that edit at the Workflow level and it will sync to every Notebook where it’s referenced.

When you’re ready to create your first Notebook, navigate to Warp Drive and click the + icon to start a new Notebook. (Or, use the keyboard shortcut SHIFT + OPTION + CMD + J)

We’re working on some nice enhancements for Notebooks including better linkability across objects in Warp Drive and permalinks so you can link out to Warp Notebooks from your docs in other apps.