|
| 1 | +# Design Documents |
| 2 | +https://github.com/acemint/x-admin-backend/docs |
| 3 | + |
| 4 | +# Contributing |
| 5 | +## Setup |
| 6 | +- Required Java Version JDK 21 |
| 7 | +- (Optional) - Install podman to run locally |
| 8 | + |
| 9 | +## Commit Convention |
| 10 | +THis document outlines how to write commit messages such that it is easier for yourself and others to track what you have changed. |
| 11 | +Adapted from [here](https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13#examples) |
| 12 | + |
| 13 | +### Commit Format: |
| 14 | +``` |
| 15 | +<type>: <description> |
| 16 | +\n |
| 17 | +<optional body> |
| 18 | +\n |
| 19 | +<optional footer> |
| 20 | +``` |
| 21 | + |
| 22 | +### Examples: |
| 23 | +``` |
| 24 | +feat: add email notifications on new direct messages |
| 25 | +``` |
| 26 | + |
| 27 | +``` |
| 28 | +feat: remove ticket list endpoint |
| 29 | +
|
| 30 | +refers to JIRA-1337 |
| 31 | +
|
| 32 | +BREAKING CHANGES: ticket enpoints no longer supports list all entites. |
| 33 | +``` |
| 34 | + |
| 35 | +### Type |
| 36 | +Essentially defines the type of change that is made |
| 37 | +- `feat` Commits, that adds or remove a new feature |
| 38 | +- `fix` Commits, that fixes a bug |
| 39 | +- `refactor` Commits, that rewrite/restructure your code, however does not change any API behaviour |
| 40 | +- `perf` Commits are special refactor commits, that improve performance |
| 41 | +- `style` Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc) |
| 42 | +- `test` Commits, that add missing tests or correcting existing tests |
| 43 | +- `docs` Commits, that affect documentation only |
| 44 | +- `build` Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ... |
| 45 | +- `ops` Commits, that affect operational components like infrastructure, deployment, backup, recovery, ... |
| 46 | +- `chore` Miscellaneous commits e.g. modifying .gitignore |
| 47 | + |
| 48 | +### Description |
| 49 | +Describe what changed you made in one sentence |
| 50 | + |
| 51 | +- Use the imperative, present tense: "change" not "changed" nor "changes" |
| 52 | + - Think of This commit will... or This commit should... |
| 53 | +- Don't capitalize the first letter |
| 54 | +- No dot (.) at the end |
| 55 | + |
| 56 | +### Body (Optional) |
| 57 | +The body should include the motivation for the change and contrast this with previous behavior. |
| 58 | + |
| 59 | +- Use the imperative, present tense: "change" not "changed" nor "changes" |
| 60 | +- This is the place to mention issue identifiers and their relations (for example, HCN-1) |
| 61 | + |
| 62 | +### Footer (Optional) |
| 63 | +The footer should contain any information about Breaking Changes |
| 64 | + |
| 65 | +- Breaking Changes should start with the word BREAKING CHANGES: followed by space or two newlines. The rest of the commit message is then used for this. |
0 commit comments