[MAINT] Improve some tests and refactor dev experience to be in line …

…w/ dowhy (#74) * Add some more tests to m-separation * consolidate wrt dowhy to poetry tools --------- Signed-off-by: Adam Li <[email protected]>
py-why · Apr 27, 2023 · 8658c5b · 8658c5b
1 parent 6342964
commit 8658c5b
Show file tree

Hide file tree

Showing 6 changed files with 354 additions and 346 deletions.
diff --git a/.github/workflows/circle_artifacts.yml b/.github/workflows/circle_artifacts.yml
@@ -1,6 +1,7 @@
 on: [status]
 jobs:
   circleci_artifacts_redirector_job:
+    if: "${{ startsWith(github.event.context, 'ci/circleci: build_doc') }}"
     runs-on: ubuntu-20.04
     name: Run CircleCI artifacts redirector
     steps:

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
@@ -41,7 +41,7 @@ jobs:
 
       # check formatting of the code style
       - name: Check code formatting
-        run: poetry run poe check_format
+        run: poetry run poe format_check
 
       # this applies various linting
       - name: Lint codebase

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -148,11 +148,11 @@ You can verify that your code will pass certain style, formatting and lint check
 
 ``verify`` runs a sequence of tests that can also be run individually. For example, you can check code formatting with black:
 
-    poetry run poe check_format
+    poetry run poe format_check
 
 If you would like to automatically black format your changes:
 
-    poetry run poe apply_format
+    poetry run poe format
 
 You can then check for code style and general linting: