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
Copy file name to clipboardExpand all lines: .github/prompts/data_extensions_development.prompt.md
+50Lines changed: 50 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,6 +85,56 @@ Essential commands for query development:
85
85
-[codeql bqrs decode](../../resources/cli/codeql/codeql_bqrs_decode.prompt.md) - Convert binary results to text
86
86
-[codeql bqrs info](../../resources/cli/codeql/codeql_bqrs_info.prompt.md) - Inspect result metadata
87
87
88
+
### Model Pack / Data Extension Options
89
+
90
+
During development, you'll typically test data extensions with a **single query** or **unit test** — not `codeql database analyze` (which is for full analysis runs / CI).
91
+
92
+
#### Running a single query with model packs
93
+
94
+
Use `codeql query run` with `--model-packs` or `--additional-packs`:
95
+
96
+
```bash
97
+
# Use a published model pack by name against a single query
98
+
codeql query run \
99
+
--database=/path/to/db \
100
+
--model-packs=my-org/my-model-pack \
101
+
--output=results.bqrs \
102
+
-- path/to/MyQuery.ql
103
+
104
+
# Use a local (unpublished) model pack during development
|`--model-packs=<name@range>`|`codeql query run`, `codeql database analyze`| Reference published model packs by name |
133
+
|`--additional-packs=<dir>[;<dir>...]`|`codeql query run`, `codeql test run`, `codeql database analyze`| Search local directories for packs (primary mechanism for local development) |
134
+
|`--no-database-extension-packs`|`codeql database analyze`| Omit extensions bundled into the database at creation time |
135
+
|`--no-database-threat-models`|`codeql database analyze`| Omit threat model config stored in the database |
0 commit comments