Feature request

Consider this example Task:

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: resource-example
spec:
  description: Sample Task to show issues with passing parameters to resources.
  params:
    - name: RESOURCE_MEMORY_REQUEST
      type: string
      default: 1Gi
    - name: RESOURCE_MEMORY_LIMIT
      type: string
      default: 2Gi
  ste

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

In the docs -- https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#serviceaccountname -- it states that ServiceAccountName is required. In our environment an EventListener author would never know what ServiceAccounts are available so we would like to use "default" in this case or better still follow Tekton Pipelines logic -- https://github.com/tektoncd/pipeline/blob/db66eca6112

Feature request

A flag in which the tkn pipeline start return's just the name of the PipelineRun

Use case

Currently trying to make a basic smoke test pipeline that will run through and call an existing pipeline multiple times in sequence with different parameters. Currently when you run the command you get a message that is nice for a user where it gives you a command for follow

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

Having circular dependencies in the installer extensions will lead to undetermined behavior during installation. This should be handled by the installer.