Closed emeth1 closed 4 months ago
Attention: Patch coverage is 0%
with 45 lines
in your changes are missing coverage. Please review.
Project coverage is 22.76%. Comparing base (
39524b7
) to head (156be25
).
Files | Patch % | Lines |
---|---|---|
src/mappings_explorer/site_builder.py | 0.00% | 45 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-178_fix_veris_mismatch_counts/
I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.
This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-178_fix_veris_mismatch_counts/
I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.
![]()
I don't think it rebuild yet when you checked. Can you check again now and confirm whether or not you see the correct non mappable table? Thanks.
I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.
I don't think it rebuild yet when you checked. Can you check again now and confirm whether or not you see the correct non mappable table? Thanks.
I'm seeing the correct tables & pages - looks good! thank you
What changed
non_mappable
capability pages built only if the project has non_mappable comments