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

Do not auto merge package-lock.json, but treat as text file #35225

Merged
merged 1 commit into from Nov 17, 2022

Conversation

ChristophWurst
Copy link
Member

If package-lock is specified to be a binary file, it becomes impossible to diff any changes. Since we only want to prevent git from merging changes in the lockfile, we can be more specific and tell it that binary handling is only required as merge strategy.

Based on the discussion at #30714 (comment).

If package-lock is specified to be a binary file, it becomes impossible
to diff any changes. Since we only want to prevent git from merging
changes in the lockfile, we can be more specific and tell it that binary
handling is only required as merge strategy.

[skip ci]

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
@ChristophWurst ChristophWurst added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Nov 17, 2022
@ChristophWurst
Copy link
Member Author

CI doesn't run because I've added [skip ci]. There is nothing to test.

@skjnldsv
Copy link
Member

CI doesn't run because I've added [skip ci]. There is nothing to test.

Witchcraft! 🧙‍♂️

@artonge artonge merged commit ea24e2a into master Nov 17, 2022
@artonge artonge deleted the chore/package-lock-git-merge-strategy branch November 17, 2022 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish
Projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants