fix: remove now defunct test_action.yaml

Author: savente93

.github/workflows/release_schedule.yaml

@@ -10,13 +10,13 @@ jobs:
   create-artifacts:
     runs-on: ubuntu-latest
     permissions:
-        contents: write
+      contents: write
     steps:
       - name: Checkout
         uses: actions/checkout@v4
-        with: 
-            # We're going to make a tag that we can we release so we'll need the full history for that
-            fetch-depth: 0 
+        with:
+          # We're going to make a tag that we can we release so we'll need the full history for that
+          fetch-depth: 0
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
@@ -28,7 +28,7 @@ jobs:
         run: |
           python spec_zero_versions.py
       - name: setup git
-        run : |
+        run: |
           # git will complain if we don't do this first
           git config user.name "GitHub Actions Bot"
           git config user.email "<>"
@@ -38,10 +38,9 @@ jobs:
         run: |
           echo "TAG_NAME=$(date '+%Y-Q%q')" >> "$GITHUB_OUTPUT"
 
-
       - name: create tag
         env:
-            TAG_NAME: ${{ steps.tag_name.outputs.TAG_NAME }}
+          TAG_NAME: ${{ steps.tag_name.outputs.TAG_NAME }}
         run: |
           git add schedule.md chart.md schedule.json
           git commit -m "Update SPEC 0 schedule artifacts"
@@ -51,16 +50,12 @@ jobs:
       - name: Publish github release
         uses: softprops/action-gh-release@v2
         env:
-            GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
           generate_release_notes: true
-          tag_name:  ${{ steps.tag_name.outputs.TAG_NAME }}
+          tag_name: ${{ steps.tag_name.outputs.TAG_NAME }}
           make_latest: true
           files: |
             schedule.md
             chart.md
             schedule.json
-            
-
-
-

.github/workflows/test_action.yaml

@@ -3,20 +3,17 @@ description: "Based on the current SPEC 0 schedule, generate a tarball with the
 author: Sam Vente
 inputs:
   target_branch:
-    description: 'Target branch for the pull request'
+    description: "Target branch for the pull request"
     required: true
-    default: 'main'
+    default: "main"
   tool: # for now only pixi, but good to make others possible from the start
-    description: 'Which tool you use for managing your environment.'
+    description: "Which tool you use for managing your environment."
     required: true
-    default: 'pixi'
+    default: "pixi"
   token:
-    description: 'GitHub token with repo permissions to create pull requests'
+    description: "GitHub token with repo permissions to create pull requests"
     required: true
 
-
-
-
 runs:
   using: "composite"
   steps:
@@ -43,7 +40,7 @@ runs:
       shell: bash
       run: gh release download -R "savente93/spec-zero-tools" --pattern schedule.json --clobber
 
-      # make usre pixi is available
+      # make user pixi is available
     - uses: prefix-dev/[email protected]
       if: ${{ inputs.tool == 'pixi' }}
       name: Setup pixi
@@ -65,4 +62,3 @@ runs:
         body: "This PR was created automatically"
         base: ${{ inputs.target_branch }}
         branch: update-spec-0-dependencies-${{ github.run_id }}
-

action.yaml

@@ -25,11 +25,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: scientific-python/spec-zero-tools@main
-        with: 
+        with:
           token: ${{ secrets.GH_PAT }}
           target_branch: main
           tool: pixi
-
 ```
 
 Whenever the action is triggered it will open a PR in your repository that will update the dependencies of SPEC 0 to the new lower bound. For this you will have to provide it with a PAT that has write permissions in the `contents` and `pull request` scopes. Please refer to the GitHub documentation for instructions on how to do this [here](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).
@@ -38,19 +37,17 @@ To help projects stay compliant with SPEC-0, we provide a `schedule.json` file t
 
 Currently the action can take the following inputs:
 
-| Name          | Description                                                                                                 | Required |
-|---------------|-------------------------------------------------------------------------------------------------------------|----------|
-| `token`       | The token that the action will use to create and update the pull request. See [token](https://github.com/marketplace/actions/create-pull-request#token). | Yes      |
-| `tool`        | Which tool to use for managing your dependencies. Currently `pixi` is the only option.                     | No       |
-| `target_branch` | The branch to open a PR against with the updated versions. Defaults to `main`.                             | No       |
-
+| Name            | Description                                                                                                                                              | Required |
+| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| `token`         | The token that the action will use to create and update the pull request. See [token](https://github.com/marketplace/actions/create-pull-request#token). | Yes      |
+| `tool`          | Which tool to use for managing your dependencies. Currently `pixi` is the only option.                                                                   | No       |
+| `target_branch` | The branch to open a PR against with the updated versions. Defaults to `main`.                                                                           | No       |
 
 ## Limitations
 
-This project is still in progress and thus it comes with some limitations we are working on. Hopefully this will be gone by the time you read this, but currently the limitations are: 
+This project is still in progress and thus it comes with some limitations we are working on. Hopefully this will be gone by the time you read this, but currently the limitations are:
 
 - Only `pixi` is supported
 - if you have a higher bound than the one listed in SPEC 0 this is overwritten
-- higher bounds are deleted instead of maintained. 
+- higher bounds are deleted instead of maintained.
 - dependency groups are not yet supported
-