Revert "rename to remove quickstart"

This reverts commit ad8185ec5b.

README.md

@@ -89,7 +89,7 @@ An asset is a software object that models a data asset, which can be a file in y
 
 Dagster visualizes upstream and downstream dependencies vertically. Assets below other assets connected by arrows implies a dependency relationship. So we can tell from the UI that the asset `hackernews_topstories` depends on `hackernews_topstory_ids` (i.e. `hackernews_topstories` takes `hackernews_topstory_ids`'s output as an input) and `hackernews_stories_word_cloud` depends on `hackernews_topstories`.
 
-All three assets are defined [in `etl/assets/hackernews.py`](./etl/assets/hackernews.py). Typically, you'll define assets by annotating ordinary Python functions with the [`@asset`](https://docs.dagster.io/concepts/assets/software-defined-assets#a-basic-software-defined-asset) decorator.
+All three assets are defined [in `quickstart_etl/assets/hackernews.py`](./quickstart_etl/assets/hackernews.py). Typically, you'll define assets by annotating ordinary Python functions with the [`@asset`](https://docs.dagster.io/concepts/assets/software-defined-assets#a-basic-software-defined-asset) decorator.
 
 This project also comes with ways to better organize the assets:
 
@@ -133,7 +133,7 @@ Click **Show Markdown**. You'll see a word cloud of the top 500 HackerNews story
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-2-6-hackernews_word_cloud.png" />
 </p>
 
-The metadata is recorded in the `hackernews_topstories_word_cloud` asset [in `etl/assets/hackernews.py`](./etl/assets/hackernews.py). Dagster supports attaching arbitrary [metadata](https://docs.dagster.io/_apidocs/ops#dagster.MetadataValue) to asset materializations. This metadata is also be displayed on the **Activity** tab of the **Asset Details** page in the UI or in the **Asset Lineage** view after selecting an asset. From the compute logs of a run, you can click the **View Asset** to go to the **Asset Details** page.
+The metadata is recorded in the `hackernews_topstories_word_cloud` asset [in `quickstart_etl/assets/hackernews.py`](./quickstart_etl/assets/hackernews.py). Dagster supports attaching arbitrary [metadata](https://docs.dagster.io/_apidocs/ops#dagster.MetadataValue) to asset materializations. This metadata is also be displayed on the **Activity** tab of the **Asset Details** page in the UI or in the **Asset Lineage** view after selecting an asset. From the compute logs of a run, you can click the **View Asset** to go to the **Asset Details** page.
 
 <p align="center">
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-2-7-view-assets.png" />
@@ -145,7 +145,7 @@ This metadata would be useful for monitoring and maintaining the asset as you it
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-2-8-filter.png" />
 </p>
 
-In the results, you'll see that the `hackernews_topstories` asset has two metadata entries: `num_records` and `preview`. Both are defined [in `etl/assets/hackernews.py`](./etl/assets/hackernews.py), in which we record the first five rows of the output Pandas DataFrame in the `preview` metadata entry using the Markdown type. This could help debug and keep your assets easily monitored. Click **Show Markdown** to view a preview of the output data frame:
+In the results, you'll see that the `hackernews_topstories` asset has two metadata entries: `num_records` and `preview`. Both are defined [in `quickstart_etl/assets/hackernews.py`](./quickstart_etl/assets/hackernews.py), in which we record the first five rows of the output Pandas DataFrame in the `preview` metadata entry using the Markdown type. This could help debug and keep your assets easily monitored. Click **Show Markdown** to view a preview of the output data frame:
 
 <p align="center">
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-2-9-preview.png" />
@@ -157,7 +157,7 @@ Note: You'll find a `path` metadata attached to every asset. This is because ass
 
 Finally, let's refresh our plots every day so we can monitor popular topics over time. To do so, we can use [schedules](https://docs.dagster.io/concepts/partitions-schedules-sensors/schedules#schedules).
 
-We've defined a daily schedule and job in [`etl/definitions.py`](./etl/definitions.py) for all assets that are defined in the [`etl/assets/`](./etl/assets) module.
+We've defined a daily schedule and job in [`quickstart_etl/definitions.py`](./quickstart_etl/definitions.py) for all assets that are defined in the [`quickstart_etl/assets/`](./quickstart_etl/assets) module.
 
 Now, let's turn on the daily schedule within Dagster.
 
@@ -168,7 +168,7 @@ Now, let's turn on the daily schedule within Dagster.
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-3-1-schedule-off.png" />
 </p>
 
-You can now turn on the schedule switch to set up the daily job we defined in [etl/definitions.py](./etl/definitions.py).
+You can now turn on the schedule switch to set up the daily job we defined in [quickstart_etl/definitions.py](./quickstart_etl/definitions.py).
 
 <p align="center">
     <img height="500" src="https://raw.githubusercontent.com/dagster-io/dagster/master/docs/static/images/quickstarts/basic/step-3-2-schedule-on.png" />
@@ -221,8 +221,8 @@ You can specify new Python dependencies in `setup.py`.
 
 ### Testing
 
-Tests are in the `etl_tests` directory and you can run tests using `pytest`:
+Tests are in the `quickstart_etl_tests` directory and you can run tests using `pytest`:
 
 ```bash
-pytest etl_tests
+pytest quickstart_etl_tests
 ```

dagster_cloud.yaml

@@ -1,4 +1,4 @@
 locations:
-  - location_name: etl
+  - location_name: quickstart_etl
     code_source:
-      module_name: etl.definitions
+      module_name: quickstart_etl.definitions

pyproject.toml

@@ -3,5 +3,5 @@ requires = ["setuptools"]
 build-backend = "setuptools.build_meta"
 
 [tool.dagster]
-module_name = "etl.definitions"
-code_location_name = "etl"
+module_name = "quickstart_etl.definitions"
+code_location_name = "quickstart_etl"

quickstart_etl/definitions.py

@@ -42,7 +42,7 @@ my_assets = link_code_references_to_git(
     git_branch="master",
     file_path_mapping=AnchorBasedFilePathMapping(
         local_file_anchor=Path(__file__).parent,
-        file_anchor_path_in_repository="examples/etl/quickstart_etl/",
+        file_anchor_path_in_repository="examples/quickstart_etl/quickstart_etl/",
     ),
 )
 

quickstart_etl_tests/test_defs.py

@@ -1,4 +1,4 @@
-from etl.definitions import defs
+from quickstart_etl.definitions import defs
 
 
 def test_def_can_load():

setup.cfg

@@ -1,2 +1,2 @@
 [metadata]
-name = etl
+name = quickstart_etl

setup.py

@@ -1,8 +1,8 @@
 from setuptools import find_packages, setup
 
 setup(
-    name="etl",
-    packages=find_packages(exclude=["etl_tests"]),
+    name="quickstart_etl",
+    packages=find_packages(exclude=["quickstart_etl_tests"]),
     install_requires=[
         "dagster",
         "dagster-cloud",