Improve Build Pipeline

Open
#98 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
build-system, devops, release

Research direction

No files, tests, or entry points are named. Start by locating the repository's build-pipeline configuration and release-publishing entry point, then verify how draft releases and asset checksums are currently handled. Done means the pipeline publishes artifacts to the Release draft and includes SHA256 values for those assets.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

The build pipeline should automatically publish the artifacts to the Release draft, and should include the SHA256 values for the assets.

Proposed technical implementation details

No response

Dominant language
C#
Stars
317
Forks
79
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.