Julia CI (github actions with codecov) setup for package development

I am working on a package and trying to setup testing, code coverage for the package.
Got lot of advice from the following thread Easy workflow file for setting up GitHub Actions CI for your Julia package

Trying to use Github actions for running tests and getting code coverage this public repo.
This is my first package, so i did expect some learning curve in setting up the CI. After runs i get these codecov reports that have broken links, patch images and warning messages but also coverage info. Reference PR where the CI was run

Can someone help me finish this CI codecov setup ?

The CI.yml file can be seen here I have also pasted it here

name: CI

# https://discourse.julialang.org/t/easy-workflow-file-for-setting-up-github-actions-ci-for-your-julia-package/49765
on:
  push:
    branches:
      - testing
  pull_request:
    branches:
      - testing
jobs:
  test:
    name: Julia ${{ matrix.version }} - ${{ matrix.os }} - ${{ matrix.arch }}
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        version:
          - "1.6.5"
        os:
          - ubuntu-latest
        arch:
          - x64
    steps:
      - uses: actions/checkout@v2
      - uses: julia-actions/setup-julia@v1
        with:
          version: ${{ matrix.version }}
          arch: ${{ matrix.arch }}
          show-versioninfo: true
      - uses: actions/cache@v1
        env:
          cache-name: cache-artifacts
        with:
          path: ~/.julia/artifacts
          key: ${{ runner.os }}-test-${{ env.cache-name }}-${{ hashFiles('**/Project.toml') }}
          restore-keys: |
            ${{ runner.os }}-test-${{ env.cache-name }}-
            ${{ runner.os }}-test-
            ${{ runner.os }}-
      - uses: julia-actions/julia-buildpkg@v1
      - uses: julia-actions/julia-runtest@v1
      - uses: julia-actions/julia-processcoverage@v1
      - uses: codecov/codecov-action@v2
        with:
          verbose: true
          files: lcov.info

Watching this video by @tim.holy made me understand that nothing was wrong.