-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Changing code-scope to file-scope commit broke PRs #16572
Comments
Here are the steps each PR author need to do to resolve the conflicts of their PR
|
@MikeAlhayek I got the following error curl : Could not find a part of the path 'C:\temp\patchformatfiles.patch'. |
the curl command should download the remote file locally for you on |
Seem you forgot that temp inside windows folder |
error: patch failed: .editorconfig:1 |
did you try to place it on a different location that |
yes, the issue right now while executing |
I tried to use |
@sebastienros, do you have any idea how to resolve the above error? I need to resolve all the conflicts for my PRs? |
@MikeAlhayek could you please reply ASAP I'm unable to update my PRs |
Can you share the error you are experiencing? Others have reported no issues with this script |
I already list the errors above |
sorry not sure. maybe @sebastienros have some feedback on your error. |
I'm waiting .. |
|
|
It should be the same while the command read from your gist |
Hi @MikeAlhayek , Is this operation necessary? Or is it also possible to fix the conflict manually? |
@hyzx86 it’s not required. You can fix them manually if the PR does not have much many file. We shared these steps to make it easier for PRs with many changes. |
I'm still blocked by this, any idea? |
If there isn't many files, update them manually. |
Some PRs have many files |
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
Still, there's no update here |
As expected merging merging #16539 broke all existing PRs
The text was updated successfully, but these errors were encountered: