Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
75 lines (59 loc) · 3.98 KB

CONTRIBUTING.md

File metadata and controls

75 lines (59 loc) · 3.98 KB
Raw

Contributing to Daytona Integrations

This repository is a monorepo of community and partner integrations, plugins, and tools for Daytona. Each package in packages/ is versioned, released, and published independently; the apps in apps/ are standalone projects that aren't published to a registry. Contributions are welcome! ❤️

If you like the project but don't have time to contribute, you can still help by starring the repo, telling others about it, or referencing it in your own project's README.

Code of Conduct

This project is governed by the Daytona Code of Conduct. By participating, you are expected to uphold it. Please report unacceptable behavior to codeofconduct@daytona.io.

Provide feedback

Found a bug or have an idea? Please open an issue — but first check that a matching issue doesn't already exist.

What you can contribute

  • Bug fixes and new features in an existing package under packages/ or app under apps/.
  • New integrations, plugins, or tools (please open an issue first to discuss the fit).
  • Documentation improvements.

Submitting a pull request

  1. Fork the repository and create a branch for your change.
  2. Keep each PR scoped to no more than one package or app (docs-only or repo-wide changes are fine). For packages, release routing is by changed file path, not the scope text.
  3. PRs are squash-merged, so the PR title must be a Conventional Commit — e.g. feat(pi-extension): add X, fix(adk-plugin): handle Y. That title becomes the squash commit that release-please reads to decide the version bump and changelog.
  4. Sign off every commit with git commit -s to comply with the DCO (see Licensing).
  5. Develop within the package's own folder — each is self-contained, with its own dependency manifest and LICENSE. Run that package's lint/build/test before opening the PR.
  6. Open the pull request (a draft PR is welcome for early feedback). A Daytona team member will review it, and once approved and green it will be merged into main.

The first time you open a PR, our CLA assistant will also comment with a link to the Contributor License Agreement and a one-line instruction to sign it (see Licensing).

Licensing

This repository is made available under Apache-2.0, unless a package declares otherwise — each package includes its own LICENSE (a few are MIT). Contributing involves two steps:

  1. DCO sign-off (per commit). Sign off every commit with git commit -s to certify, under the Developer Certificate of Origin v1.1, that you have the right to submit the code. The sign-off email must match the commit author's email. A DCO check runs on every pull request.

  2. CLA signature (once). You must also sign the Daytona Contributor License Agreement — it covers both individual and entity/corporate contributors. You (or, for entity contributors, your organization) retain copyright in your contributions, but you grant Daytona Platforms, Inc. a perpetual, irrevocable, sublicensable license to them — including the right to relicense and redistribute the software under any terms (open source, proprietary, or closed source) and to change the license or visibility of the project at any time. A CLA assistant bot will comment on your first pull request with a link and a one-line instruction to sign; a single signature covers all your future contributions to this repository.

Your PR cannot be merged until both the DCO check and the CLA check are green.