chore: only run coverage once

[zachdaniel]

Contributor checklist

• My commit messages follow the Conventional Commit Message Format
  For example: fix: Multiply by appropriate coefficient, or
  feat(Calculator): Correctly preserve history
  Any explanation or long form information in your commit message should be
  in a separate paragraph, separated by a blank line from the primary message
• Bug fixes include regression tests
• Features include unit/acceptance tests

[github-actions]

Pull Request Test Coverage Report for Build 444b91da25c0cbe607a5db79cb53ad51d3a01227-PR-2

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 0.0%

---

Totals
Change from base Build 67d4de5547e0eb4643d505dbe944f4dd5c7df06e:	0.0%
Covered Lines:	0
Relevant Lines:	99

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 444b91da25c0cbe607a5db79cb53ad51d3a01227-PR-2

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 0.0%

---

Totals
Change from base Build 67d4de5547e0eb4643d505dbe944f4dd5c7df06e:	0.0%
Covered Lines:	0
Relevant Lines:	99

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 444b91da25c0cbe607a5db79cb53ad51d3a01227-PR-2

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 0.0%

---

Totals
Change from base Build 67d4de5547e0eb4643d505dbe944f4dd5c7df06e:	0.0%
Covered Lines:	0
Relevant Lines:	99

---

💛 - Coveralls