Contribution Guidelines
Categories:
Thank you for your interest in contributing to Texera! This guide explains how to contribute to both Texera’s codebase and documentation.
We follow a fork-based workflow and adopt the Conventional Commits standard for commit messages.
Contributing to Texera
Texera welcomes contributions from everyone — whether you’re fixing a small bug, improving documentation, or adding new features.
👥 Roles in the Project
| Role | Key Permissions | How to Join |
|---|---|---|
| Contributor | Submit issues & PRs, join discussions | Start contributing — no formal process |
| Committer | Merge PRs, push code, vote on code changes | Nominated by PPMC based on quality contributions |
| PPMC Member | Governance, release voting, new committer approvals | Voted by existing PPMC members |
| Mentor | Guide project and ensure Apache compliance | Appointed by the Incubator PMC |
🛠 How to Contribute Code
1. Fork the Repository
Fork the Texera repository on GitHub and clone it locally.
2. Find or Open an Issue
- Pick an existing issue or create a new one describing your proposal or bug.
- Discuss your approach with committers before coding to reach consensus.
3. Create and Submit a Pull Request
Develop in a new branch of your fork.
Modifying the SQL schema?
Be sure to updatesql/changelog.xmlby adding a new<changeSet>element.When ready, submit a PR to the main Texera repository.
Allow edits from maintainers to let committers make small fixes if needed.
PR Title and Commit Format
We use Conventional Commits:
- Example PR titles:
feat: add new join operatorfix(frontend): resolve workflow panel crashchore(deps): bump dependency versions
- The PR title becomes the final squashed commit message upon merge.
A scope names the module the change lands in — amber, pyamber, frontend, agent-service, file-service, and so on. Use the module’s own name rather than an informal synonym, and when a PR spans modules, scope it to the one carrying the substantive change.
Pick the type by what happens to the behavior, not by how large the change is:
| Your change | Type |
|---|---|
| A functionality worked before and no longer does | fix |
| A functionality or a form of support never existed and you are adding it | feat |
| A functionality exists and you are removing support for it | feat |
| A functionality is reworked in a way that intentionally changes user-facing behavior | feat |
| The change leaves the user-facing behavior unchanged | refactor |
Behavior is defined by the code, not by what a document or an old PR description says the code does. A functionality that was never implemented does not exist, so implementing it is a feat even when the docs already described it as present.
refactor claims the user-facing behavior is identical. A test that pins a user-facing API must keep passing untouched — changing one of its assertions means the behavior moved, so the PR is a feat or a fix. A test that pins internals mirrors the implementation and may be rewritten alongside the code it mirrors.
Test and dependency PRs take the titles below. Where the table shows a two-part scope, it is written as <type>(<area>, <module>): <description>:
| Your change | Title |
|---|---|
| A test-only PR — adding or updating tests | test(<module>): ... |
| Repairing a broken or flaky test | fix(test, <module>): ... |
| A dependency bump that patches a CVE | fix(deps, <module>): ... |
| Any other dependency bump | chore(deps, <module>): ... |
Omit the module for bumps that span modules. GitHub Actions bumps are dependency bumps too and take the ci module — chore(deps, ci): ..., or fix(deps, ci): ... when the bump patches a CVE — which is the form Renovate opens them with. Reserve a bare ci: ... for hand-written CI and workflow changes.
A PR targeting a release branch appends the version as the last scope component — a backport of fix(deps, frontend): ... to release/v1.2 becomes fix(deps, frontend, v1.2): .... Never put a version tag on a PR targeting main.
PR Description Should Include:
- Purpose: use
Closes #1234to auto-close an issue. - Summary: short overview of your changes.
- Optional: design document, technical diagram, or screenshots.
Avoid including:
- Local config files (e.g.,
python_udf.conf) - Secrets or credentials
- Binary or build artifacts
🧪 Testing and Quality Checks
Backend (Scala)
- Run lint:Fix with:
sbt "scalafixAll --check"sbt scalafixAll - Run formatter:Fix with:
sbt scalafmtCheckAllsbt scalafmtAll - Execute tests:
sbt test
For IntelliJ users: ensure the working directory matches the module (
amberfor engine tests, the repo root for services).
Frontend (Angular)
- Run unit tests:
cd frontend ng test --watch=false - Format code:
yarn format:fix
Write .spec.ts tests for new functionality to ensure future safety.
🔍 Pull Request Review Process
- Request a committer to review your PR.
- Add labels (e.g.,
fix,enhancement,docs). - Wait for CI to pass (GitHub Actions).
- Mark your PR as draft if it’s not ready.
- Once approved, a committer will merge your PR.
📝 Apache License Header
All new files must include the Apache License header.
To automate this in IntelliJ:
- Go to Settings → Editor → Copyright → Copyright Profiles.
- Create a profile named Apache and add:
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership... - Set this as the default profile for the project.
✍️ Contributing to Documentation
Texera uses Hugo and the Docsy theme to build its website.
All documentation is stored in the Texera GitHub repository.
Quick Steps
- Click Edit this page at the top of any doc page to edit directly on GitHub.
- Make your edits and open a Pull Request.
- The site auto-deploys a preview for review via Netlify.
- Wait for approval and merge.
Preview Locally
To preview locally:
hugo server
Visit http://localhost:1313 to view the site as you edit.
📚 Resources
- Texera GitHub Repository
- Conventional Commits Spec
- Hugo Documentation
- Docsy Guide
- GitHub Pull Request Docs
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.