hovancik/stretchly

[Feature Request]: Include Winget Packages in Release Process

Open

#1,338 opened on Jun 22, 2023

View on GitHub
 (6 comments) (1 reaction) (0 assignees)JavaScript (410 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (3,892 stars)
PR merge metrics
 (Avg merge 2d 7h) (14 merged PRs in 30d)

Description

Version

  • I'm using version 1.14.1

Existing requests

  • I've checked Existing requests

Advanced Preferences

  • I've checked Advanced Preferences

What operating system are you using?

Windows

Operating System Version

Windows 11 version 22H2

Problem description

I would like to request the addition of Winget packages to the release process of the Strectchly repository.

Possible solution

I propose that with each new release of Strectchly, a corresponding Winget package is also created and made available. This would greatly simplify the installation process for users who prefer using Winget as their package manager.

Alternative solutions

Instead of creating and maintaining Winget packages alongside the regular releases, an alternative solution could be to provide a script or tool that automates the process of generating Winget manifests for Strectchly.

Additional information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Investigate how to create Winget manifests and integrate them into the Stretchly release pipeline.
Tech stack
javascript
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70