Windowscommunitytoolkit: Proposal: More human friendly names for PR preview packages

[chingucoding]

Currently, the PR preview packages have catchy version names like 7.0.0-build.608.gf80a107340 and 7.0.0-build.568.gd64fb3b95d making it difficult to select the correct package if one wants to try out a specific PR package. A good way to improve the experience would be to have the version also include the PR number so people don't have to go through the CI and check what the latest version for the specific PR is.

[msftbot[bot]]

Hello chingucoding, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

@chingucoding Thanks for the suggestion.

@Sergio0694 do you want to work on this one?

[Sergio0694]

@Kyaa-dost I'm pretty busy working on #3639 at this moment, and I'm afraid I'm not exactly a CI expert either 😅

I think I remember @michael-hawker saying making the preview packages better wasn't possible right now due to how the names were being automatically generated by Nerdbank.GitVersioning, but he'll surely be able to add more info about that.

[Kyaa-dost]

@Sergio0694 no worries, totally understand. Will wait on this one as it doesn't seem like an urgent change.

[michael-hawker]

Thanks @chingucoding! This is something that I wanted to do when we setup the new pipeline. It was a bit complicated with use using the Nerdbank Versioning as it takes the info from the original commit hash, so it's hard to update inline with this system.

You can see my previous attempt in #3532. Maybe after 7.0 we can adopt a different system over nerdbank which would allow this.

For now, you can compare the hash from the bottom of a PR and grab the same package as we call out in our Wiki 🙂