test renmaing

.github/workflows/update_to_dune.yml → .github/workflows/push_to_dune.yml

@@ -1,4 +1,4 @@
-name: Update to Dune on Commit (Push Queries)
+name: Push to Dune on Commit
 
 on:
   push:

README.md

@@ -9,16 +9,20 @@ A template for creating repos to manage your Dune queries using the CRUD API.
 
 2. Copy and paste that list into the `queries.yml` file. 
 
-3. Install the python requirements and run the `update_from_dune.py` script. You can input the following lines into a terminal/CLI:
+3. Install the python requirements and run the `pull_from_dune.py` script. You can input the following lines into a terminal/CLI:
 
 ```
 pip install -r requirements.txt
-python scripts/update_from_dune.py
+python scripts/pull_from_dune.py
 ```
 
 This will bring in your query ids into `query_{id}.sql` files within the `queries` folder. You can run that same python script again anytime you need to update your work from Dune into this repo.
 
-4. Make any changes you need to directly in the repo, and any time you push a commit, `update_to_dune.py` will run and save your changes into Dune directly. We use the [Dune CRUD API](https://dune.com/docs/api/api-reference/edit-queries/) to manage queries - note that this does not change how your queries behave in app.
+4. Make any changes you need to directly in the repo, and any time you push a commit, `push_to_dune.py` will run and save your changes into Dune directly. We use the [Dune CRUD API](https://dune.com/docs/api/api-reference/edit-queries/) to manage queries - note that this does not change how your queries behave in app. You can also do this without waiting for a commit/github action by running the script manually:
+
+```
+python scripts/push_to_dune.py
+```
 
 ### For Contributors