Skip to content
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

doc: contribute: distinguish renaming new versus old files #84177

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

marc-hb
Copy link
Collaborator

@marc-hb marc-hb commented Jan 17, 2025

Address a concern raised by @de-nordic in the review of commit 3756f59 ("doc: contribution guidelines: Clarify and extend")

Address a concern raised by @de-nordic in the review of commit
3756f59 ("doc: contribution guidelines: Clarify and extend")

Signed-off-by: Marc Herbert <[email protected]>
Copy link
Member

@nashif nashif left a comment

Choose a reason for hiding this comment

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

i think the statement as it is right now is accurate, this is talking about commits within a PR.

Copy link
Collaborator

@de-nordic de-nordic left a comment

Choose a reason for hiding this comment

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

@marc-hb Thanks for bringing this up.

I think that this addition is a nod in direction of reviewers.

I had often had to review code/doc updates done via move-change and often had to download pr and pass file through a script to find me changes in moved, and often indented, block.


* The history remains clean and easy to follow.
* Bisectability is preserved by eliminating redundant renaming or partial rewrites.

Note renaming and changing code *older* than the Pull Request is a different situation. To
help git rename detection heuristics, it's better to minimize changes to code that is being
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe just note that this helps reviewers rather than git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants