user_troubleshooting_message: Include git commit of the vcpkg repo and suggest updating with git pull

[autoantwort]

Currently you can only guess if the user is using a recent vcpkg version when a user submits an issue.

[strega-nil-ms]

Is there a reason we aren't just using rev-parse HEAD?

[autoantwort]

Because I want to know the date. I want to know if the user is using a recent version of the vcpkg repo or an old one. And only the hash does not help (Yeah I can lookup the commit and check the date, but doing this for every issue is very painful).

[dg0yt]

How does it interact with custom registries or overlay ports? They may change the given port and/or dependencies.

[autoantwort]

How does it interact with custom registries or overlay ports? They may change the given port and/or dependencies.

Thats right, my ultimate goal is that vcpkg outputs a ready to copy paste github issue markdown code. In that you can then also put config files and other important information. The only problem currently is to catch the error logs. They are printed here:
https://github.com/microsoft/vcpkg/blob/827a54c404e67205262e6db032fb2c1a5e6fd097/scripts/cmake/vcpkg_execute_required_process.cmake#L132
I would simply search for the See logs for more information string but I assume @strega-nil-ms wants a guid based solution?

[autoantwort]

@BillyONeal can you do the second review ? :)