Skip to content

Latest commit

 

History

History
66 lines (41 loc) · 4.08 KB

PREPARING_YOUR_CHANGES.md

File metadata and controls

66 lines (41 loc) · 4.08 KB
Raw

Preparing Your Changes

This document contains information related to preparing changes for a pull request. Here's a quick checklist for a good PR, more details below:

  1. A discussion around the change on Slack or in an issue.
  2. A GitHub Issue with a good description associated with the PR
  3. One feature/change per PR
  4. One commit per PR
  5. PR rebased on main (git rebase, not git pull)
  6. Good descriptive commit message, with link to issue
  7. No changes to code not directly related to your PR
  8. Includes functional/integration test
  9. Includes documentation

Commit Message Format

We do not require a particular commit message format of any kind, but we do require that individual commits be descriptive, relative to size and impact. For example, if a descriptive title covers what the commit does in practice, then an additional description below the title is not required. However, if the commit has an out-sized impact relative to other commits, its description will need to reflect that.

Reviewers may ask you to amend your commits if they are not descriptive enough. Since the descriptiveness of a commit is subjective, please feel free to talk to us on Slack if you have any questions.

Optional Commit Template

If you would like an optional commit template, see the following:

<present-tense-verb-with-capitalized-first-letter> <everything-else-without-punctuation-at-the-end>

<sentences-in-paragraph-format-or-bullet-points>

Squashed Commits

We require that you squash all changes to a single commit. You can do this with the git rebase -i HEAD~X command where X is the number of commits you want to squash. See the Git Documentation for more details.

Developer's Certificate of Origin

Any contributions to Daytona must only contain code that can legally be contributed to Daytona, and which the Daytona project can distribute under its license.

Prior to contributing to Daytona please read the Developer's Certificate of Origin and sign-off all commits with the --signoff option provided by git commit. For example:

git commit --signoff --message "This is the commit message"

This option adds a Signed-off-by trailer at the end of the commit log message.

DCO Policy on Real Names

The DCO is a representation by someone stating they have the right to contribute the code they have proposed and is important for legal purposes. We have adopted the CNCF DCO Guidelines (https://github.com/cncf/foundation/blob/main/dco-guidelines.md). Which for simplicity we will include here in full:

DCO Guidelines v1.1

The DCO is a representation by someone stating they have the right to contribute the code they have proposed for acceptance into a project: https://developercertificate.org

That representation is important for legal purposes and was the community-developed outcome after a $1 billion lawsuit by SCO against IBM. The representation is designed to prevent issues but also keep the burden on contributors low. It has proven very adaptable to other projects, is built into git itself (and now also GitHub), and is in use by thousands of projects to avoid more burdensome requirements to contribute (such as a CLA).

DCO and Real Names

The DCO requires the use of a real name that can be used to identify someone in case there is an issue about a contribution they made.

A real name does not require a legal name, nor a birth name, nor any name that appears on an official ID (e.g. a passport). Your real name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution.

Your real name should not be an anonymous id or false name that misrepresents who you are.