-
Notifications
You must be signed in to change notification settings - Fork 0
App Workbench
Benedict Albrecht edited this page Jun 3, 2026
·
6 revisions
The Workbench tab lists all your workbenches. A workbench connects a Template to a GitHub repository and produces a pull request.
flowchart LR
A[Select Repo] --> B[Select Template]
B --> C[Create Workbench]
C --> D[Parsing]
D --> E[Browse & Select]
E --> F[PR into GitHub]
- Switch to the Workbench tab
- Enter a name in the text field at the bottom (e.g.,
pythontest0106) - Click create
Crodox parses the linked repository using the selected Template. The header shows the Repository and Project ID for the active workbench.
Once parsing completes, the workbench view shows two panels:
| Panel | Content |
|---|---|
| Left - File tree | Parsed files and folders, expanded into their grammar objects (e.g., comment_block, import, parameter). Each node has a checkbox for selection. |
| Right - Detail view | Content of the selected file or object. Shows the actual code matched by the grammar. |
- Expand folders and files to see the parsed structure down to individual grammar objects
- Use the toggle in the top right to switch views
- Check files or objects to select them for a pull request
After selecting files and objects with the checkboxes:
- Crodox uses the Dependency Structure to ensure the PR is coherent
- The PR is pushed to your linked GitHub repository
See also: Template - Write grammar definitions · GitHub Integration - Link your account
- Getting Started
- Sign-Up
- Home Screen
- Creating Your First Template
- Template Editor
- Application Navigation
- Syntax Overview
- Workflow: End-to-End
- Workflow: Test with simpleDemo
- Workflow: Build Template from angularTemp
- Demo Repositories
- Template
- Workbench
- GitHub Integration
- GitHub App Installation
- GitHub Repository Setup
- GitHub Re-linking
- Settings
- Overview
- Declarations
- Types
- Scoping