Code of Conduct
Before you start contributing, you must read and abide by our Code of Conduct.Getting Started
To start contributing to Tekton code:- Set up your development environment - see the Development Guide
- Understand the architecture - see the Architecture Overview
- Review the development standards and processes in the Tekton community repo
Development Standards
The Tekton community repository contains important information on:-
Development standards:
- Writing high quality code
- Adopting good development principles
- Writing useful commit messages
-
Development processes:
- Finding things to work on
- Proposing new features
- Performing code reviews
- Becoming a community member and maintainer
- Contacting other contributors
Tekton Pipelines Resources
- GitHub Project - Track project progress and milestones
- Roadmap - Upcoming features and priorities
- API Compatibility Policy - Guidelines for API changes
- Topical Ownership - Contact owners for specific areas
Slash Commands
The project includes GitHub slash commands to automate common workflows:/cherry-pick
Automatically cherry-picks a merged PR to one or more target branches. Usage:/cherry-pick <target-branch> [<target-branch2> ...]
Examples:
/cherry-pick release-v0.47.x/cherry-pick release-v0.47.x release-v1.3.x
- PR must be merged
- User must have write permissions
- Target branch(es) must exist
/rebase
Rebases a PR branch against its base branch and force pushes the result. Usage:/rebase
Requirements:
- PR must be open
- PR must not be from a fork (branch must be in tektoncd/pipeline)
- User must have write permissions
--force-with-lease for safe force pushing.
Contributing to Documentation
If you want to contribute to Tekton documentation, see the Tekton Documentation Contributor’s Guide. The guide includes:- The contribution process for documentation
- Standards for writing high quality content
- Formatting conventions
- A primer for getting started with writing documentation