feat(scoop-update): Stash uncommitted changes before update

[niheaven]

Description

Auto stash uncommitted changes of scoop before update.

Now the action is done in scoop core, should this be applied to buckets too?

Motivation and Context

• Relates to feat(scoop-(un)hold): Support scoop (un)hold scoop #5089 (comment)

How Has This Been Tested?

And this could be tested by checking out this PR, adding some dummy files in scoop dir and running scoop update.

Checklist:

• I have read the Contributing Guide.
• I have ensured that I am targeting the develop branch.
• I have updated the documentation accordingly.
• I have updated the tests accordingly.
• I have added an entry in the CHANGELOG.

[rashil2000]

I think you missed the -C $currentdir flag.

But on a second note, stashing changes is an unexpected behaviour for users. I think it is just better to fail the update (and Git automatically shows the reason why the update failed). It is important to let users know they have uncommitted changes, fail gracefully, and then let the user decide whether to stash the changes themselves.

Now the action is done in scoop core, should this be applied to buckets too?

Bucket update sometimes fail due to EOL conflicts, this change will create multiple stashes there and somewhat pollute the working tree.

[niheaven]

I'll add a config option to control it: stash, prompt, cancel.

Bucket update sometimes fail due to EOL conflicts, this change will create multiple stashes there and somewhat pollute the working tree.

Sometimes the stashes should be removed easily then git reset and bucket rm/add lol

[niheaven]

Done.

[niheaven]

Any other comments? This should be merged now.