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

Preserve info from files with matching SHA-1s #6990

Merged

Conversation

rubennorte
Copy link
Contributor

Summary

The current implementation of the watchman crawler ignores any previous information for files with different modification time. This modifies that part to also preserve the information for files with the same sha-1.

Test plan

Updated the test suite.

@mjesun mjesun changed the title Preserve info from files with matching sha-1 Preserve info from files with matching SHA-1s Sep 17, 2018
Copy link
Contributor

@mjesun mjesun left a comment

Choose a reason for hiding this comment

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

LGTM. Please fix the linting error before merging.

@rubennorte rubennorte force-pushed the preserve-file-data-for-matching-sha1 branch from 38c79fa to 5c8456a Compare September 17, 2018 16:09
@SimenB
Copy link
Member

SimenB commented Sep 17, 2018

Changelog? 😁

@rubennorte
Copy link
Contributor Author

@SimenB I never add them in the first commit because I need the PR number, and then I always forget 😅

@SimenB
Copy link
Member

SimenB commented Sep 17, 2018

The lint failure CI complains about has been fixed on master, so this PR is actually green

@rubennorte rubennorte force-pushed the preserve-file-data-for-matching-sha1 branch from 5c8456a to 89f97d1 Compare September 17, 2018 17:17
@rubennorte rubennorte merged commit 628a3d1 into jestjs:master Sep 17, 2018
@rubennorte rubennorte deleted the preserve-file-data-for-matching-sha1 branch September 17, 2018 18:28
@mjesun
Copy link
Contributor

mjesun commented Sep 19, 2018

@rubennorte Why is this breaking?

@rubennorte
Copy link
Contributor Author

@mjesun it's not. The breaking part is just a typo in the previous message.

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants