[Spike] Investigate Code Coverage Changes in Registry Support

[Jdubrick]

Which area/kind this issue is related to?

/area registry

Issue Description

As discussed in the comments in devfile/registry-support#199 the Code Coverage report is being severely impacted by any changes that require generated code files to grow in content. These generated code files should be excluded as they are not testable by us. As part of the above PR there was an addition to add files ending in .gen.go to be excluded from the coverage report, however, the reports are still failing because it is not changing the previous reports. This is causing the report to be expecting those files to be covered, even if we are now ignoring them.

Investigation will need to be done into Code Coverage to see if there is a way to either remove those generated files from previous reports, or force it to ignore them moving forward.

Code Coverage Report
Change For Exclusion

Acceptance Criteria

• Find possible solutions to solving the issue of code coverage reports incorrectly looking for coverage for generated code files in registry-support

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.