|
| 1 | +# Contributing to Kubeflow Notebooks |
| 2 | + |
| 3 | +Welcome to the Kubeflow Notebooks project! |
| 4 | +Contributions are welcome via GitHub pull requests. |
| 5 | + |
| 6 | +Please see the [Contributing to Kubeflow](https://www.kubeflow.org/docs/about/contributing/) page for more information. |
| 7 | + |
| 8 | +## Sign Your Work |
| 9 | + |
| 10 | +To certify you agree to the [Developer Certificate of Origin](https://developercertificate.org/) you must sign-off each commit message using `git commit --signoff`, or manually write the following: |
| 11 | + |
| 12 | +```text |
| 13 | +feat(ws): my commit message` |
| 14 | +
|
| 15 | +Signed-off-by: John Smith <john-smith@users.noreply.github.com> |
| 16 | +``` |
| 17 | + |
| 18 | +## Use Semantic Commits |
| 19 | + |
| 20 | +We use [semantic commits](https://www.conventionalcommits.org/en/v1.0.0/) to help us automatically generate changelogs and release notes. |
| 21 | + |
| 22 | +### Prefixes |
| 23 | + |
| 24 | +A semantic commit message must start with one of the following __prefixes__: |
| 25 | + |
| 26 | +- `fix:` (bug fixes) |
| 27 | +- `feat:` (new features) |
| 28 | +- `improve:` (improvements to existing features) |
| 29 | +- `refactor:` (code changes that neither fixes a bug nor adds a feature) |
| 30 | +- `revert:` (reverts a previous commit) |
| 31 | +- `test:` (adding missing tests, refactoring tests; no production code change) |
| 32 | +- `ci:` (changes to CI configuration or build scripts) |
| 33 | +- `docs:` (documentation only changes) |
| 34 | +- `chore:` (ignored in changelog) |
| 35 | + |
| 36 | +To indicate a breaking change, add `!` after the prefix, e.g. `feat!: my commit message`. |
| 37 | + |
| 38 | +### Scopes |
| 39 | + |
| 40 | +You may optionally include a __scope__ after the prefix, for example: |
| 41 | + |
| 42 | +- `nb` (changes to notebooks - web-app, controller, images) |
| 43 | +- `pvc` (changes to volumes - web-app, controller) |
| 44 | +- `tb` (changes to tensorboards - web-app, controller) |
| 45 | +- `ws` (changes to workspaces - frontend, backend, controller, images) |
| 46 | + |
| 47 | +### Examples |
| 48 | + |
| 49 | +Here are some examples of semantic commit messages: |
| 50 | + |
| 51 | +- `fix(nb): something that was broken` |
| 52 | +- `feat(ws): a new feature` |
| 53 | +- `improve: a general improvement` |
| 54 | +- `chore: update readme` |
0 commit comments