Multiline comment break the /test [ci-job-name] command for Tekton based jobs

[afrittoli]

Expected Behavior

I can enter a multi-line comment in GitHub that includes /test [ci-job-name] by itself on one line

Actual Behavior

Multi-line comment breaks the logic of the check condition:

  # If no command was specified, the check is successful
  [[ "$(inputs.params.gitHubCommand)" == "" ]] && exit 0

Steps to Reproduce the Problem

1. Leave a multi-line comment on an issue that includes /test
2. Observe the condition logs
3. https://dashboard.dogfooding.tekton.dev/#/namespaces/tektonci/taskruns/tekton-yamllint-x9cm5-lint-cg6gj-check-name-matches-1-77fm4?step=condition-check-check-name-matches&view=logs

https://dashboard.dogfooding.tekton.dev/#/namespaces/tektonci/taskruns/tekton-yamllint-x9cm5-lint-cg6gj-check-name-matches-1-77fm4?step=condition-check-check-name-matches&view=logs

Additional Info

[afrittoli]

/kind bug

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/lifecycle frozen
We need to handle that case

[afrittoli]

We do! Honestly, I'd love to have a CELRun based solution and remove that condition for good :)