codecov[bot]
commented
3 weeks ago Codecov Report
Attention: Patch coverage is 25.00000% with 9 lines in your changes missing coverage. Please review.
Project coverage is 64.57%. Comparing base (
3f9bcd0) to head (c7e0d3f).
| Files | Patch % | Lines |
|---|---|---|
| pkg/cmd/tknpac/info/install.go | 25.00% | 8 Missing and 1 partial :warning: |
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #1706 +/- ## ========================================== - Coverage 64.59% 64.57% -0.03% ========================================== Files 144 144 Lines 11151 11158 +7 ========================================== + Hits 7203 7205 +2 - Misses 3422 3427 +5 Partials 526 526 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This commit modifies the 'install' command to allow non-admin users to retrieve installation information for Pipelines-as-Code. Previously, this command was restricted to admin users only. Now, if the user does not have rights to list all repos in the cluster, the command will attempt to list repos in the current namespace instead. The command's help text has been updated to reflect this change.
Changes
Submitter Checklist
[x] 📝 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).
[x] ♽ 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.
[x] ✨ 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.
[x] 🧪 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).