I cannot export patch files.

[Wout01]

Every time I try to patch one I get this:" WARNING Latest version of Firefox (89.0) does not match frozen version (87.0).
00:00:00 Wiping patches directory...

00:00:00 Exporting modified files...
(node:9880) UnhandledPromiseRejectionWarning: Error: Command failed with exit code 128: git ls-files -m --ignored --exclude-standard
fatal: ls-files -i must be used with either -o or -c
at makeError (C:\Users\lieve\browser-ff\node_modules\execa\lib\error.js:60:11)
at handlePromise (C:\Users\lieve\browser-ff\node_modules\execa\index.js:118:26)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async getFiles (C:\Users\lieve\browser-ff.dotbuild\commands\export-patches.js:20:31)
at async exportModified (C:\Users\lieve\browser-ff.dotbuild\commands\export-patches.js:47:34)
at async Object.exportPatches [as controller] (C:\Users\lieve\browser-ff.dotbuild\commands\export-patches.js:120:5)
(node:9880) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:9880) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Does anyone know if I'm doing something wrong? Or someone who has a solution for this?

[kierandrewett]

Are you running this in Git Bash or cmd?

[Wout01]

Git Bash

[Wout01]

Do you have a solution for this?

[kierandrewett]

Not currently, I am seeing if anyone can reproduce this issue on Windows.

[Wout01]

Okay, thanks for the help. Also try to find a solution for this.

[trickypr]

This isn't an issue with windows or git bash. I have experienced the same issue on my personal system when working with melon. I managed to fix this by replacing --ignore with -i -o. I am not sure if this will negatively effect melons operation, so I will not implement it on nightly. Here is the v89 and nightly branches for reference.

[Wout01]

Thanks

[trickypr]

@EnderDev Should I push this fix to nightly?