... | ... | @@ -23,7 +23,12 @@ The commit message should be structured as follows |
|
|
- Development changes
|
|
|
- **fix**: Patches a bug in the standard and directly corresponds to a PATCH release
|
|
|
- **feat**: Describes a new feature in a backwards compatible way and corresponds to a MINOR release
|
|
|
- Breaking Change: This indicates MAJOR changes that introduces breaking changes. Indicated in the commit body (see examples)
|
|
|
- Breaking Change: This indicates MAJOR changes that introduce breaking changes. Indicated in the commit body (see examples)
|
|
|
```
|
|
|
fix(docs): Remove link to TrafficSignals
|
|
|
|
|
|
Fixes #249
|
|
|
```
|
|
|
- **style**
|
|
|
commits that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
|
|
|
- **build**
|
... | ... | @@ -38,13 +43,17 @@ The scope provides additional contextual information. |
|
|
| identifier | description |
|
|
|
|---|---|
|
|
|
| **code** | OSI specification code changes|
|
|
|
| **inlinedocs** | OSI specification code changes|
|
|
|
| **docs** | Changes to accompanying documentation|
|
|
|
|
|
|
### OSC 1.x
|
|
|
| identifier | description |
|
|
|
|---|---|
|
|
|
| **model** | Domain model specification|
|
|
|
| **docs** | Accompanying user guide|
|
|
|
| **modeldocs** | HTML documentation on the model |
|
|
|
| **modelingguidelines** | Modeling guidelines for the UML model|
|
|
|
| **examples** | Accompanying examples|
|
|
|
| **userguide** | Accompanying user guide|
|
|
|
|
|
|
### OSC 2.0
|
|
|
| identifier | description |
|
... | ... | |