Every Step that Pipelines runs emits a JSON object with metadata about its execution: the content of task results, a StartedAt timestamp, step exit codes etc etc.

The JSON object is passed back to the Tekton Controller by way of the "Termination Message", a Kubernetes feature that allows a Container to write a short amount of content that ends up back in the Pod's YAML. The emphasis here is on

Describe the bug

I found this bug during investigate #2050. The problems found when we add labels until clear all button overflow to the next line. It will be shown like this:

But if we add more label, it will looks like:

Expected Behavior

All tasks in the catalog are aligned to the authoring recommendations.

Actual Behavior

Most tasks are not.

How to Address this Issue

• This does not have to be solved in one go, it could be broken down into many small tasks - feel free to open other, more specific, issues - and link them here

Expected Behavior

When a Trigger successfully creates a resources, we should emit a k8s event.

Actual Behavior

Triggers does not emit any k8s events today.

Additional Info

• We could also consider emitting events on Trigger failures -- but likely there will be many of them so this should be optional.
• Events in Pipelines: https://github.com/tektoncd/pipeline/blob/c7a60b8a77c

Feature request

add --ignore-running flag with pipelinrun and taskrun delete commands.
Currently, we can not ignore the running taskrun/pipelinerun with the delete command.

Use case

Adding this will help delete all the pipelineruns/taskruns ignoring the running ones.
Combined with other flags would

To make it easier for users to interact with the Gitea admin UI

The landing page could use a few improvements:

• change the title to "Welcome to Tekton"
• expand more on the initial paragraph
  • inline part of the concepts page, add a diagram or two
  • we could add a list of projects with a one sentence description about each
• the "what's next" does not seem to add much value, I would remove it
• rending of the TOC below seems broken, there is too