Conversation
1 task
3 tasks
Member
|
Running |
13 tasks
This was referenced Apr 25, 2022
This was referenced May 6, 2022
1 task
This was referenced Jul 16, 2022
arcanis
added a commit
that referenced
this pull request
Aug 24, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's the problem this PR addresses?
The
yarn patch-commitcommands generates an incorrect configuration which often results in the patch not being correctly applied without tweaking the config.How did you fix it?
The command will now be smarter in the configuration it generates. In particular:
resolutions)resolutionsfield will reference the correct original range(s) rather than an arbitrary oneA few other things are also improved:
~/prefix, in which case it'll be relative to the project rootyarn patchcommand now supports a-uflag which will reapply existing patchesChecklist