Skip to content

Commit 01b9e7a

Browse files
committed
workflow: add request to rewrite the history
When commit history provide sufficient details for a user, we might request updating the commit history. This often happens for adding new functionality or changing the current one without explaining why are we changing it or how to use a new one.
1 parent 28d6393 commit 01b9e7a

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/reference/contributing/guidelines/workflow.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,8 @@ Pull requests on GitHub have to meet the following requirements to keep the code
6464
- Comment in the pull request on every change (rebase or new commits). This helps reviewers to be up to date with changes
6565
- Pull requests should fix a bug, add a feature or refactor.
6666

67+
If commits do not follow above guidelines, you might be requested to modify the commit history (it is often adding more details to address _what_ and _why_ vs _how_).
68+
6769
#### Release versioning
6870

6971
You can find Mbed OS versioning at [How We Release Arm Mbed OS](../introduction/how-we-release-arm-mbed-os.html).

0 commit comments

Comments
 (0)