# Repository CR
This page describes the Repository custom resource (CR), which is the central configuration object for Pipelines-as-Code. Every Git repository you onboard to Pipelines-as-Code requires a corresponding Repository CR that defines the connection, authentication, and behavioral settings.

## Overview

The Repository CR is a namespaced Kubernetes resource. You can reference it using the short name `repo`.

```yaml
apiVersion: pipelinesascode.tekton.dev/v1alpha1
kind: Repository
metadata:
  name: my-repository
  namespace: my-namespace
spec:
  url: "https://github.com/owner/repo"
  git_provider:
    type: github
    secret:
      name: github-token
      key: token
```

## Resource structure

<a id="param-api-version"></a>

### `apiVersion` — `string` — required


Identifies the API version for the Repository resource. Must be `pipelinesascode.tekton.dev/v1alpha1`.



<a id="param-kind"></a>

### `kind` — `string` — required


Identifies the resource kind. Must be `Repository`.



<a id="param-metadata"></a>

### `metadata` — `ObjectMeta` — required


Standard Kubernetes metadata, including name, namespace, labels, and annotations.



<a id="param-spec"></a>

### `spec` — `RepositorySpec` — required


Defines the desired behavior of the repository. See [Repository Spec](/nightly/docs/api/repository-spec.md) for detailed field documentation.



## Resource shortcuts

The Repository CR supports the following short name:

- `repo` - Short form for `repository`

```bash
# List all repositories
kubectl get repo

# Describe a specific repository
kubectl describe repo my-repository
```

## Custom columns

When you list repositories with `kubectl get repo`, the following columns appear:

- **URL** -- The Git repository URL
- **Succeeded** -- Success status of the last PipelineRun
- **Reason** -- Reason for the last PipelineRun status
- **StartTime** -- When the last PipelineRun started
- **CompletionTime** -- When the last PipelineRun completed

## Complete example

```yaml
apiVersion: pipelinesascode.tekton.dev/v1alpha1
kind: Repository
metadata:
  name: example-repo
  namespace: pipelines-as-code
  labels:
    app: my-app
spec:
  url: "https://github.com/organization/repository"
  concurrency_limit: 5
  git_provider:
    type: github
    url: "https://github.com"
    user: "pac-bot"
    secret:
      name: github-app-secret
      key: github-app-token
    webhook_secret:
      name: webhook-secret
      key: webhook-token
  incoming:
    - type: webhook-url
      secret:
        name: incoming-webhook-secret
        key: token
      params:
        - version
        - environment
      targets:
        - main
  params:
    - name: deployment_env
      value: "production"
      filter: "event == 'push' && target_branch == 'main'"
    - name: api_key
      secret_ref:
        name: api-credentials
        key: key
  settings:
    pipelinerun_provenance: "source"
    github_app_token_scope_repos:
      - "organization/other-repo"
    gitops_command_prefix: "/my-prefix"
    policy:
      ok_to_test:
        - "trusted-user"
        - "maintainer"
      pull_request:
        - "contributor"
    github:
      comment_strategy: "update"
    gitlab:
      comment_strategy: "update"
      token_auto_rotation: true
    forgejo:
      user_agent: "my-custom-agent"
      comment_strategy: "update"
    ai:
      enabled: true
      provider: openai
      secret_ref:
        name: llm-api-token
        key: token
      roles:
        - name: failure-analysis
          prompt: "Analyze the CI/CD pipeline failure"
          model: "gpt-5.4-mini"
          on_cel: "pipelinerun_status == 'Failed'"
          output: pr-comment
          context_items:
            error_content: true
            container_logs:
              enabled: true
              max_lines: 100
```

## Related resources

- [Repository Spec](/nightly/docs/api/repository-spec.md) -- Detailed specification fields
- [Settings Reference](/nightly/docs/api/settings.md) -- Settings configuration options