Create codacy-coverage-reporter.yaml

[codecakes]

added code coverage reporter from codacy which attaches coverage results.

Summary by Sourcery

CI:

• Adds a new CI workflow to report code coverage to Codacy.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces a new GitHub Actions workflow, codacy-coverage-reporter.yaml, to automatically report code coverage to Codacy. The workflow is triggered on pushes and pull requests to the main branch. It checks out the code and then uses the codacy-coverage-reporter-action to upload coverage reports to Codacy, using a project token stored as a secret.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added a new GitHub Actions workflow to report code coverage to Codacy.	Created codacy-coverage-reporter.yaml workflow file. Configured the workflow to trigger on push and pull request events to the main branch. Added a job to run on ubuntu-latest. Configured the job to checkout the code using actions/checkout@v3. Added a step to run the codacy-coverage-reporter-action@v1.3.0. Passed the Codacy project token as a secret. Specified htmlcov as the coverage report format.	.github/workflows/codacy-coverage-reporter.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codacy-production]

⚠️ Codacy found a medium Security issue: An action sourced from a third-party repository on GitHub is not pinned to a full length commit SHA. Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release.

The issue highlighted by the Semgrep linter is that the GitHub Action codacy/codacy-coverage-reporter-action@v1.3.0 is being referenced by a version tag (v1.3.0) rather than a full-length commit SHA. Using a version tag can lead to potential security vulnerabilities as the code associated with that tag may change in the future. Pinning to a specific commit SHA ensures that the action remains immutable and that the same code is executed every time, reducing the risk of unexpected behavior or security issues.

To fix this issue, you should replace the version tag with the full-length commit SHA of the version you want to use. You can find the commit SHA by looking at the repository's release history on GitHub.

Assuming the commit SHA for version v1.3.0 is abcdef1234567890abcdef1234567890abcdef12, the change would look like this:

Suggested change

	uses: codacy/codacy-coverage-reporter-action@v1.3.0
	uses: codacy/codacy-coverage-reporter-action@abcdef1234567890abcdef1234567890abcdef12

---

This comment was generated by an experimental AI tool.