Fix release-note formatting

[dibyom]

Changes

There was an added space between the backticks and the release-note string
See #5093

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs included if any changes are user facing
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please ask for approval from dibyom after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dibyom]

/kind misc

[abayer]

This was a deliberate move by @vdemeester to make sure the release note checker wouldn’t pass if someone just didn’t change anything in the release note section.

[afrittoli]

This was a deliberate move by @vdemeester to make sure the release note checker wouldn’t pass if someone just didn’t change anything in the release note section.

The alternative could be to have this job running against pipeline https://dashboard.dogfooding.tekton.dev/#/namespaces/tekton-ci/pipelineruns/check-github-tasks-completed-dxg7f?pipelineTask=github-tasks-completed

[dibyom]

This was a deliberate move by @vdemeester to make sure the release note checker wouldn’t pass if someone just didn’t change anything in the release note section.

Yes, the release checker doesn't pass but I've found that as a reviewer I still have to point out removing the space (or just do it myself). We already mention filling out the release notes in the Submitter checklist and I was hoping that would be enough? (The automated check also sounds good).

[tekton-robot]

@dibyom: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-tekton-pipeline-unit-tests	a450e05	link	true	/test tekton-pipeline-unit-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[afrittoli]

/test check-pr-has-kind-label

[tekton-robot]

@afrittoli: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-tekton-pipeline-alpha-integration-tests
• /test pull-tekton-pipeline-build-tests
• /test pull-tekton-pipeline-integration-tests
• /test tekton-pipeline-unit-tests

The following commands are available to trigger optional jobs:

• /test pull-tekton-pipeline-go-coverage

Use /test all to run all jobs.

In response to this:

/test check-pr-has-kind-label

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afrittoli]

/test pull-tekton-pipeline-unit-tests

[tekton-robot]

@afrittoli: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-tekton-pipeline-alpha-integration-tests
• /test pull-tekton-pipeline-build-tests
• /test pull-tekton-pipeline-integration-tests
• /test tekton-pipeline-unit-tests

The following commands are available to trigger optional jobs:

• /test pull-tekton-pipeline-go-coverage

Use /test all to run all jobs.

In response to this:

/test pull-tekton-pipeline-unit-tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dibyom]

See #5171 for the flaky unit test fix

[vdemeester]

🤔 maybe we should not even have the release-note part in the template then 🤔

[jerop]

#5308