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: docs/integrations/github.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@
5
5
The GitHub Actions CI/CD Bot enables teams to automate their SQLMesh projects using GitHub Actions. It can be configured to perform the following things:
6
6
7
7
* Automatically run unit tests on PRs
8
+
* Automatically run the linter on PRs
8
9
* Automatically create PR environments that represent the code changes in the PR
9
10
* Automatically categorize and backfill data for models that have changed
10
11
* Automatically deploy changes to production with automatic data gap prevention and merge the PR
@@ -350,6 +351,7 @@ These can be used to potentially trigger follow up steps in the workflow.
350
351
These are the possible outputs (based on how the bot is configured) that are created by the bot:
351
352
352
353
* `run_unit_tests`
354
+
* `linter`
353
355
* `has_required_approval`
354
356
* `pr_environment_synced`
355
357
* `prod_plan_preview`
@@ -373,6 +375,8 @@ In addition, there are custom outputs listed below:
373
375
* `created_pr_environment` - set to `"true"` (a string with a value of `true`) if a PR environment was created for the first time. It is absent, or considered empty string if you check for it, if it is not created for the first time
374
376
* `pr_environment_name` - the name of the PR environment. It is output whenever PR environment synced check reaches a conclusion. Therefore make sure to check the status of `created_pr_environment` or `pr_environment_synced` before acting on this output
375
377
378
+
Note: The `linter` step will run only if it's enabled in the project's configuration (`config.yaml` / `config.py`). The step will fail if the linter finds errors, otherwise it'll output only the warnings.
379
+
376
380
## Custom Workflow Configuration
377
381
You can configure each individual action to run as a separate step. This can allow for more complex workflows or integrating specific steps with other actions you want to trigger. Run `sqlmesh_cicd github` to see a list of commands that can be supplied and their potential options.
378
382
```bash
@@ -460,6 +464,10 @@ jobs:
460
464
## Example Screenshots
461
465
### Automated Unit Tests with Error Summary
462
466

467
+
### Automated Linting with Error Summary
468
+

469
+
### Automated Linting with Warning Summary
470
+

463
471
### Automatically create PR Environments that represent the code changes in the PR
0 commit comments