The task Resolver link should not be the same as the Bundle link.
Change Resolver link to https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#specifying-remote-tasks
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).
[x] ๐ 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.
[x] ๐ If feasible, please check if an end-to-end test can be added. See README for more details.
[x] ๐ 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).
The task
Resolver
link should not be the same as theBundle
link.Change
Resolver
link tohttps://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#specifying-remote-tasks
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).
[x] ๐ 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.
[x] ๐ If feasible, please check if an end-to-end test can be added. See README for more details.
[x] ๐ 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).