scripts: west_commands: patch: Add gh-fetch subcommand

[pdgendt]

Add a gh-fetch subcommand to the west patch extension to download a patch file from Github and generate the patch meta data.

The patch info is appended to the patches.yml file.

[cfriedt]

Cool 😎

[pdgendt]

I'm thinking the gh-fetch subcommand should create the patches file and directory if they don't exist yet.

@cfriedt WDYT?

[cfriedt]

@pdgendt - yeah that makes sense. And possibly append to the file as well.

[faxe1008]

Tangential to this command: perhaps one that goes through all patches and alerts you if a patch was merged upstream. :^)

[pdgendt]

Tangential to this command: perhaps one that goes through all patches and alerts you if a patch was merged upstream. :^)

Not sure if the west patch needs to become another Swiss army knife, having the gh-fetch was to reduce the amount of work to create a patch from a PR which could get tedious.

[cfriedt]

@faxe1008 - I could see something like west patch prune.

Effectively, all it would do is check the merge-pr URL to see if a patch was merged, and delete the patch from yaml if it was.

[faxe1008]

@faxe1008 - I could see something like west patch prune.

Effectively, all it would do is check the merge-pr URL to see if a patch was merged, and delete the patch from yaml if it was.

Yeah that would be lovely, altough this means that ideally the patch is only pruned if the west manifest of the project points to a commit that includes the commit of the merged PR. Or alternatively after pruning it gives you the "next" revision that includes all pruned patches. But I guess for the first case applying the patches will fail anyways 🤷