CommunityToolkit/WindowsCommunityToolkit

Proposal: More human friendly names for PR preview packages

Open

#3,642 opened on Dec 20, 2020

View on GitHub
 (7 comments) (2 reactions) (0 assignees)C# (1,403 forks)batch import
CI/pipeline 🔬help wantedimprovements :sparkles:

Repository metrics

Stars
 (5,708 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Explore the build pipeline where PR preview package versions are generated and modify the versioning to include the PR number.
Tech stack
csharp
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60