Skip to content

workflow: add request to rewrite the history #887

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Jan 3, 2019

Review: @ARMmbed/mbed-os-maintainers

@0xc0170 0xc0170 force-pushed the dev_workflow_rewrite_git_log branch from a91759e to 0cf91ac Compare January 3, 2019 08:15
Copy link
Contributor

@NirSonnenschein NirSonnenschein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks ok, I suggested one small change.

@@ -64,6 +64,8 @@ Pull requests on GitHub have to meet the following requirements to keep the code
- Comment in the pull request on every change (rebase or new commits). This helps reviewers to be up to date with changes
- Pull requests should fix a bug, add a feature or refactor.

If commits do not follow above guidelines, you might be requested to rewrite the history (it is often adding more details to address _what_ and _why_ vs _how_).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: requested to rewrite the history -> requested to modify the commit history

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed

@0xc0170 0xc0170 force-pushed the dev_workflow_rewrite_git_log branch from 0cf91ac to 184613d Compare January 3, 2019 08:20
@0xc0170
Copy link
Contributor Author

0xc0170 commented Jan 3, 2019

@cmonr This shoud address you question about when we request changes to the commit history

@0xc0170 0xc0170 force-pushed the dev_workflow_rewrite_git_log branch from 184613d to 01b9e7a Compare January 3, 2019 08:24
When commit history does not provide sufficient details for a reader, we might request updating the commit history.
This often happens for new functionality or changing the current one without explaining why are we changing it or
how to use a new one.

Good example that would lead to change request in the PR is "Initial version for new feature" one-liner in the commit history.
@0xc0170 0xc0170 force-pushed the dev_workflow_rewrite_git_log branch from 01b9e7a to ea13dae Compare January 3, 2019 08:25
@0xc0170
Copy link
Contributor Author

0xc0170 commented Jan 3, 2019

I added some details to the commit msg

Copy link
Contributor

@NirSonnenschein NirSonnenschein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Make minor edits for precise language.
@AnotherButler AnotherButler merged commit f1934a0 into ARMmbed:development Jan 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants