From 4da28c46cd3270bca1d3100c6cadc2d721821b2f Mon Sep 17 00:00:00 2001 From: Pedram Navid <1045990+PedramNavid@users.noreply.github.com> Date: Thu, 15 Aug 2024 08:55:45 -0700 Subject: [PATCH] update titles --- docs/docs-next/docs/guides/automation/asset-sensors.md | 6 +++++- .../guides/automation/running-pipelines-on-a-schedule.md | 4 +--- docs/docs-next/docs/guides/automation/schedules.md | 6 +++++- docs/docs-next/docs/guides/automation/sensors.md | 8 ++++++-- .../automation/triggering-pipeline-runs-using-events.md | 4 +--- 5 files changed, 18 insertions(+), 10 deletions(-) diff --git a/docs/docs-next/docs/guides/automation/asset-sensors.md b/docs/docs-next/docs/guides/automation/asset-sensors.md index 63a0b1419acae..27d27ce1f8591 100644 --- a/docs/docs-next/docs/guides/automation/asset-sensors.md +++ b/docs/docs-next/docs/guides/automation/asset-sensors.md @@ -1,5 +1,9 @@ +--- +title: Asset Sensors +--- + ### Basic Asset Sensor Example -This Asset Sensor will trigger a run of `my_job` whenever the `asset_to_watch` asset is materialized. \ No newline at end of file +This Asset Sensor will trigger a run of `my_job` whenever the `asset_to_watch` asset is materialized. diff --git a/docs/docs-next/docs/guides/automation/running-pipelines-on-a-schedule.md b/docs/docs-next/docs/guides/automation/running-pipelines-on-a-schedule.md index c99994d5c9a78..acd4159ad27dc 100644 --- a/docs/docs-next/docs/guides/automation/running-pipelines-on-a-schedule.md +++ b/docs/docs-next/docs/guides/automation/running-pipelines-on-a-schedule.md @@ -1,6 +1,4 @@ --- -title: "Scheduling runs" +title: "Scheduling pipelines" sidebar_position: 1 --- - -# Scheduling runs \ No newline at end of file diff --git a/docs/docs-next/docs/guides/automation/schedules.md b/docs/docs-next/docs/guides/automation/schedules.md index 6eb7464b4fd6b..8e394b2964cf4 100644 --- a/docs/docs-next/docs/guides/automation/schedules.md +++ b/docs/docs-next/docs/guides/automation/schedules.md @@ -1,7 +1,11 @@ +--- +title: Scheduling Examples +--- + ### Basic Schedule Example For more examples of schedules, see the [How-To Use Schedules](/guides/automation/schedules) guide. -For more information about how Schedules work, see the [About Schedules](/concepts/schedules) concept page. \ No newline at end of file +For more information about how Schedules work, see the [About Schedules](/concepts/schedules) concept page. diff --git a/docs/docs-next/docs/guides/automation/sensors.md b/docs/docs-next/docs/guides/automation/sensors.md index 976b44d698bb5..fcaa64aa5be7c 100644 --- a/docs/docs-next/docs/guides/automation/sensors.md +++ b/docs/docs-next/docs/guides/automation/sensors.md @@ -1,4 +1,8 @@ -### Basic Sensor Example +--- +title: Sensor Examples +--- + +### Basic Sensor Example This example includes a `check_for_new_files` function that simulates finding new files. In a real scenario, this function would check an actual system or directory. @@ -11,4 +15,4 @@ The sensor runs every 5 seconds. If it finds new files, it starts a run of `my_j By default, sensors aren't enabled when first deployed to a Dagster instance. Click "Automation" in the top navigation to find and enable a sensor. -::: \ No newline at end of file +::: diff --git a/docs/docs-next/docs/guides/automation/triggering-pipeline-runs-using-events.md b/docs/docs-next/docs/guides/automation/triggering-pipeline-runs-using-events.md index a22694860e3fa..6886e2946584c 100644 --- a/docs/docs-next/docs/guides/automation/triggering-pipeline-runs-using-events.md +++ b/docs/docs-next/docs/guides/automation/triggering-pipeline-runs-using-events.md @@ -1,6 +1,4 @@ --- -title: "Triggering runs using events" +title: "Creating event-based pipelines" sidebar_position: 2 --- - -# Triggering pipeline runs using events \ No newline at end of file