🗑️ Remove publish.yml

We no longer use publish for anything. And if we want to do some sort
of coverage testing, it may make sense to have a dedicated repo with
actions for this sort of testing.

.github/workflows/library_check.yml

@@ -78,11 +78,3 @@ jobs:
       source_dir: ${{ inputs.source_dir }}
       repo: ${{ inputs.repo }}
     secrets: inherit
-
-  publish_artifacts:
-    needs: [lint, tests]
-    uses: ./.github/workflows/publish.yml
-    with:
-      library: ${{ inputs.library }}
-      repo: ${{ inputs.repo }}
-    secrets: inherit

.github/workflows/tests.yml

@@ -147,10 +147,3 @@ jobs:
       #     $(cat code-coverage-results.md |
       #     grep -Eo 'https://img.shields.io/badge/[^)]*')
       #     -O build/coverage/coverage.svg
-
-      - uses: actions/[email protected]
-        if: github.ref == 'refs/heads/main' && github.repository == inputs.repo
-        with:
-          name: coverage
-          retention-days: 1
-          path: build/coverage/

README.md

@@ -38,18 +38,14 @@ The repository contains the following workflows:
    platform. It installs necessary dependencies, sets up Conan profiles, and
    builds the package for the specified platform.
 
-9. `publish.yml`: Used to publish the library. It generates a badge for the
-    latest version of the library, sets up GitHub Pages, and deploys the
-    documentation to GitHub Pages.
+9. `self_check.yml`: Used to run a series of checks on various libraries to
+   determine if all of the workflows still work as intended.
 
-10. `self_check.yml`: Used to run a series of checks on various libraries to
-    determine if all of the workflows still work as intended.
-
-11. `take.yml`: Used to assign issues to contributors. When a
+10. `take.yml`: Used to assign issues to contributors. When a
     contributor comments on an issue with the word "take", the workflow assigns
     the issue to the contributor.
 
-12. `tests.yml`: Used to run tests on the library. It installs
+11. `tests.yml`: Used to run tests on the library. It installs
     necessary dependencies, sets up Conan profiles, builds the library, runs
     tests, and optionally generates code coverage reports.