3 Commits

View File

@@ -43,6 +43,7 @@ necessary) and merged into the project.
1. Your branch name should be as short as possible, but describes your changes
2. Words should be divided by minus sign (`-`)
3. Optionally, might starts with general [type](#types) of your future PR
with slash (`/`): `refactor/nasm-to-fasm`, `update/demos`, `fix/cp866-charset`
## Commit style
@@ -50,7 +51,7 @@ necessary) and merged into the project.
The commit message should look like this:
```test
```
type(scope): commit message header
Commit message body, if needed
@@ -89,17 +90,19 @@ Commit message body, if needed
### Scopes
> [!INFO]
> [!NOTE]
> Scopes are optional
- `krn` - kernel
- `drv` - drivers
- `lib` - libraries
- `app` - userspace applications
- `skin` - skins
- `data` - images, configs, resources, etc.
| Scope | Description |
| :----: | :------------------------------- |
| `krn` | kernel |
| `drv` | drivers |
| `lib` | libraries |
| `app` | userspace applications |
| `skin` | skins |
| `data` | images, configs, resources, etc. |
> [!INFO]
> [!NOTE]
> If changes are made to a specific component, the name of the component
> separated by `/` character needs to be specified. For example:
> `app/shell`, `lib/libimg`