Add a /debug command to see what the bots know about a particular issue/PR

[tumido]

Is your feature request related to a problem? Please describe.
Time to time I'm setting up the CI process using the Thoth bots for analytics repos. While doing so, I sometimes run into issues which results in a build failure/task not being triggered properly or failing unnoticed etc. Sometimes these errors goes unreported in the release issue and I'm met with a silent treatment from the bots. It's hard to debug it that way and I always have to bother @harshad16 who must be really annoyed by my requests by now.

Describe the solution you'd like
I prefer to get my hands dirty so if the issue is obvious and easily fixable I would like to do that on my own without putting more work on @harshad16's plate. It would be nice if we can have a chat-ops command, like /debug or something, which would force sesheta to respond with a list of what it knows about that particular issue/PR:

• What tekton pipelines were triggered - with links to the job runs, because it's hard/slow to determine which namespace/thoth runtime is actually the prod now (when there were multiple thoth0*.lab.upshift deployments) and then which of the pipeline run actually is triggered from "my" repo (since they are all named the same, you have to open them all)
• Current CI configuration it can parse out of that particular repo
• If the proper GitHub apps are set up on the repo, etc.

Describe alternatives you've considered
Bother the Thoth team every time:

• I use python3.8 Pipfile and try to build it via a python3.6 pipeline
• I'm not the maintainer in the CI config (this is being reported by now already)
• I'm using the wrong base image for the build
• Sesheta is not privileged enough to write to the repo
• Having typos in the config

Additional context
thoth-station/kebechet#629, aicoe-aiops/mailing-list-analysis-toolkit#18

Issues which resulted in dead silence from the bots and we had hard time debugging it:
aicoe-aiops/mailing-list-analysis-toolkit#16
aicoe-aiops/mailing-list-analysis-toolkit#15
aicoe-aiops/categorical-encoding#15
aicoe-aiops/categorical-encoding#16
aicoe-aiops/categorical-encoding#17
aicoe-aiops/categorical-encoding#19
AICoE/s2i-custom-notebook#19

[goern]

/kind feature
/priority important-longterm
/label hacktoberfest

[sesheta]

@goern: The label(s) /label hacktoberfest cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, deployment_name/ocp-test, deployment_name/ocp-stage, deployment_name/moc, thoth/group-programming, thoth/potential-observation, sig/documentation, sig/cyborgs, sig/investigator, sig/indicators, sig/knowledge-graph, sig/solvers, sig/slo, sig/advisor, sig/build, sig/devops

In response to this:

/kind feature
/priority important-longterm
/label hacktoberfest

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.

[goern]

@tumido is this still required/valid?

[tumido]

I'd still "want" to have that option to be notified at what stage my job is, yes.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

[harshad16]

/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[harshad16]

/lifecycle frozen