tkn pac create Create a new Pipelines-as-Code Repository custom resource definition.
Synopsis tkn pac create repository [flags] tkn pac create repo [flags]
Description The create repository command creates a new Pipelines-as-Code Repository CRD that links a Git repository to your Kubernetes cluster. It will:
Prompt for namespace (or create if it doesn’t exist)Prompt for Git repository URL Create the Repository CRD Configure webhook (if not using GitHub App)Generate sample PipelineRun in .tekton/ directory
The generated PipelineRun targets the main branch with pull_request and push events.
Usage Examples Interactive Mode
With Repository Name
With URL
With Namespace
Full Example
From Current Directory
# Create repository interactively tkn pac create repo
Interactive Prompts When running without flags, you’ll be prompted for:
1. Git Repository URL If run from a Git repository, the URL is auto-detected:
Enter the Git repository URL (default: https://github.com/myorg/myapp):
2. Target Namespace Choose where PipelineRuns will execute:
Please enter the namespace where the pipeline should run (default: myapp-pipelines):
If the namespace doesn’t exist:
⚠️ Namespace production-pipelines is not found Would you like me to create the namespace production-pipelines? (Y/n)
3. Webhook Configuration If GitHub App is not configured:
? Select your Git provider: › GitHub GitLab Bitbucket Cloud Bitbucket Server Forgejo ? Enter your personal access token: **** ? Enter webhook secret: ****
Flags Repository name (defaults to auto-generated from URL)
Git repository URL (e.g., https://github.com/org/repo)
Target namespace where PipelineRuns will be created
Namespace where Pipelines-as-Code is installed
Output Example $ tkn pac create repo Enter the Git repository URL (default: https://github.com/myorg/myapp ): Please enter the namespace where the pipeline should run (default: myapp-pipelines ): production ✓ Namespace production has been created ✓ Repository myorg-myapp has been created in production namespace ? Select your Git provider: GitHub ? Enter your personal access token: **** ? Enter webhook secret ( leave empty to auto-generate ): ✓ Webhook configured on https://github.com/myorg/myapp ✓ Secret git-provider-secret has been created ℹ️ Directory .tekton has been created. ✓ A basic template has been created in .tekton/pipelinerun.yaml, feel free to customize it. ℹ️ You can test your pipeline by pushing the generated template to your git repository
Generated Files .tekton/pipelinerun.yaml A sample PipelineRun is created:
apiVersion : tekton.dev/v1 kind : PipelineRun metadata : name : myapp-pull-request annotations : pipelinesascode.tekton.dev/on-event : "[pull_request, push]" pipelinesascode.tekton.dev/on-target-branch : "[main]" spec : pipelineSpec : tasks : - name : fetch-repository taskRef : name : git-clone resolver : hub workspaces : - name : output workspace : source params : - name : url value : "{{ repo_url }}" - name : revision value : "{{ revision }}" workspaces : - name : source emptyDir : {}
Repository CRD Structure The created Repository CRD:
apiVersion : "pipelinesascode.tekton.dev/v1alpha1" kind : Repository metadata : name : myorg-myapp namespace : production spec : url : "https://github.com/myorg/myapp" git_provider : secret : name : "git-provider-secret" key : "token" webhook_secret : name : "webhook-secret" key : "webhook-secret"
Webhook Configuration GitHub App (No Configuration Needed) If a GitHub App is configured, webhooks are handled automatically:
✓ Repository myorg-myapp has been created in production namespace ✓ A basic template has been created in .tekton/pipelinerun.yaml
Manual Webhook Setup For other providers or GitHub webhook mode:
Token : Personal access token or API keyWebhook Secret : Shared secret for webhook validationWebhook URL : Automatically configured on Git provider
Provider-Specific Configuration GitHub Required token scopes:
repo - Full control of repositoriesadmin:repo_hook - Manage webhooks
GitLab Required token scopes:
api - Full API accessread_repository - Read repository
Bitbucket Cloud Required:
App password with repository:write and webhook permissions
Bitbucket Server Required:
Personal access token with REPO_ADMIN permission
Auto-Detection Features Git URL Detection When run from a Git repository:
cd ~/projects/myapp tkn pac create repo # Auto-detects: https://github.com/myorg/myapp
Namespace Suggestion Default namespace based on current context or repository name:
Current namespace: default Suggested namespace: myapp-pipelines
Repository Name Generation Auto-generated from Git URL:
URL: https://github.com/myorg/myapp Name: myorg-myapp
Common Workflows Create and Push # Create repository tkn pac create repo --url https://github.com/myorg/myapp # Customize the generated PipelineRun vim .tekton/pipelinerun.yaml # Commit and push git add .tekton/ git commit -m "Add Pipelines-as-Code configuration" git push # Create a pull request to test gh pr create --title "Test PAC" --body "Testing Pipelines-as-Code"
Multiple Repositories # Create multiple repositories in the same namespace tkn pac create repo --url https://github.com/myorg/api --namespace shared-pipelines tkn pac create repo --url https://github.com/myorg/ui --namespace shared-pipelines tkn pac create repo --url https://github.com/myorg/docs --namespace shared-pipelines
Different Namespaces per Environment # Development tkn pac create repo --url https://github.com/myorg/myapp --namespace dev-pipelines # Staging tkn pac create repo --url https://github.com/myorg/myapp --namespace staging-pipelines # Production tkn pac create repo --url https://github.com/myorg/myapp --namespace prod-pipelines
Troubleshooting Namespace Already Exists If the namespace exists but you don’t have access:
Error: namespaces "production" is forbidden
Solution : Request access or use a different namespace.Invalid Git URL Error: invalid git URL: not-a-valid-url
Solution : Provide a valid HTTPS Git URL:tkn pac create repo --url https://github.com/myorg/myapp
Repository Already Exists Error: repositories.pipelinesascode.tekton.dev "myorg-myapp" already exists
Solution : Delete the existing repository first or use a different name:tkn pac delete repo myorg-myapp # or tkn pac create repo --name myorg-myapp-v2
PAC Not Installed Error: pipelines-as-code is not installed in the cluster
Solution : Run bootstrap first:See Also