codecov[bot]
commented
6 months ago Codecov Report
Attention: Patch coverage is 88.46154% with 3 lines in your changes are missing coverage. Please review.
Project coverage is 64.18%. Comparing base (
c703cd8) to head (2fe253b).
| Files | Patch % | Lines |
|---|---|---|
| pkg/resolve/resolve.go | 85.71% | 2 Missing and 1 partial :warning: |
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #1637 +/- ## ========================================== + Coverage 64.09% 64.18% +0.09% ========================================== Files 140 140 Lines 10897 10921 +24 ========================================== + Hits 6984 7010 +26 + Misses 3380 3378 -2 Partials 533 533 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
The validation errors occurring in PipelineRuns as reported by the tekton controller within the .tekton directory are now reported directly in the event logs of the user namespaces along with the pipelinerun name where the error has occurred, this let a user troubleshoot the issue even if she or he doesn't have access to the controller log.
https://issues.redhat.com/browse/SRVKP-4318
Changes
Submitter Checklist
[ ] 📝 Please ensure your commit message is clear and informative. For guidance on crafting effective commit messages, refer to the How to write a git commit message guide. We prefer the commit message to be included in the PR body itself rather than a link to an external website (ie: Jira ticket).
[ ] ♽ Before submitting a PR, run make test lint to avoid unnecessary CI processing. For an even more efficient workflow, consider installing pre-commit and running pre-commit install in the root of this repository.
[ ] ✨ We use linters to maintain clean and consistent code. Please ensure you've run make lint before submitting a PR. Some linters offer a --fix mode, which can be executed with the command make fix-linters (ensure markdownlint and golangci-lint tools are installed first).
[ ] 📖 If you're introducing a user-facing feature or changing existing behavior, please ensure it's properly documented.
[ ] 🧪 While 100% coverage isn't a requirement, we encourage unit tests for any code changes where possible.
[ ] 🎁 If feasible, please check if an end-to-end test can be added. See README for more details.
[ ] 🔎 If there's any flakiness in the CI tests, don't necessarily ignore it. It's better to address the issue before merging, or provide a valid reason to bypass it if fixing isn't possible (e.g., token rate limitations).