microsoft / microsoft/winget-pkgs
[New Feature]: Create GitHub release on each Publish
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
On each publish, I'd like to see a GitHub release created that matches the version of the MSIX package that is published. I'd like this release to include the automatically generated release notes that indicate which commits were included as part of the release.
Proposed technical implementation details (optional)
The release doesn't necessarily have to contain the source.msix and source2.msix files, but it would be nice.
Ideally, this could replace the Publish-Pipeline-Succeeded label and comment as the notification for each PR would happen through the automatically generated release notes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or workflow entry point is named. Start by locating the repository's publish automation and documenting how the MSIX version and published artifacts are exposed; done means each publish creates a matching GitHub release with generated release notes, with source.msix and source2.msix handled according to the chosen scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100